Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Sa 29.06.2024 00:01:13 61.915 +2 3.501.982 56,6 Fosstodon 4.2.9 500 Fr 28.06.2024 00:01:07 61.913 +3 3.498.459 56,5 Fosstodon 4.2.9 500 Do 27.06.2024 00:00:32 61.910 0 3.495.444 56,5 Fosstodon 4.2.9 500 Mi 26.06.2024 00:00:07 61.910 +1 3.494.703 56,4 Fosstodon 4.2.9 500 Di 25.06.2024 00:00:06 61.909 +1 3.491.246 56,4 Fosstodon 4.2.9 500 Mo 24.06.2024 00:00:01 61.908 +1 3.488.299 56,3 Fosstodon 4.2.9 500 So 23.06.2024 00:00:06 61.907 +5 3.485.556 56,3 Fosstodon 4.2.9 500 Sa 22.06.2024 00:00:08 61.902 0 3.482.735 56,3 Fosstodon 4.2.9 500 Fr 21.06.2024 00:00:09 61.902 +6 3.481.405 56,2 Fosstodon 4.2.9 500 Do 20.06.2024 00:00:08 61.896 0 3.479.101 56,2 Fosstodon 4.2.9 500
(@gurchik) · 02/2022 · Tröts: 69 · Folger: 8
Sa 29.06.2024 18:47
Always set an imagePullPolicy on your deployments.
While investigating an issue, I noticed 2 applications, which used the same Deployment spec, had different imagePullPolicies. It was because their spec didn't specify a policy. When this happens, Kubernetes has different behavior depending on the image tag. https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting
My suggestion is to always specify one, as it isn't intuitive for the default to be different depending on circumstances that can later change.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0