You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a few applications that are set to run as "latest" image ( I know, we should not - but we do).
Once written to ECR, this "latest" will stay there forever ... so it will soon become "not latest".
From reading #843 , it seems some users have decided to wipe all images via ECR policy to force this - which introduces quite some issues (PullImageBackOff namely).
What about adding a new setting like "max_image_days" (default to "0" for infinite, to avoid changing current deployments) ? then k8s-image-swapper could just push again when it reaches that max_age.
The text was updated successfully, but these errors were encountered:
Hi,
We have a few applications that are set to run as "latest" image ( I know, we should not - but we do).
Once written to ECR, this "latest" will stay there forever ... so it will soon become "not latest".
From reading #843 , it seems some users have decided to wipe all images via ECR policy to force this - which introduces quite some issues (PullImageBackOff namely).
What about adding a new setting like "max_image_days" (default to "0" for infinite, to avoid changing current deployments) ? then k8s-image-swapper could just push again when it reaches that max_age.
The text was updated successfully, but these errors were encountered: