Time out policy #4
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It is not an acceptable risk. Breaking things without some user action is poor practice. Can we find out how many images are out there which have images older than 365 days? And if any of them are in use? |
|
|
ecr_old_images_20250404_133458.xlsx |
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Had an ad-hoc meeting with Security/OIS and they requested a new ECR policy to expire images that are older than a year.
I mentioned this can break clusters that have been out in the env for a long time if they are not actively maintained, and that was an acceptable risk from their perspective, with the addition that a cluster shouldn't exist without maintenance for over a year.
Not sure how to test this directly, but
tf validatepassed.