Create a Delayed Release Process about bottlerocket HOT 4 OPEN

Thanks for cutting this issue @misterek! I think this is similar to #2805. I think the main difference is providing this as distinct SSM parameters for things like Karpenter vs doing something in the OS. I think there is value in having each issue since they solve the problem differently but end with the same result of having a way to control the velocity of updates.

from bottlerocket.

You are 100% right, it is similar. Apologize for not finding that one.

Probably the core issue is figuring out how to keep track of a history of releases and release dates. I was thinking of that with distinct SSM parameters, but perhaps that would make a better feature for Karpenter (search for AMI's by xyz parameters, and use the one that was most recent as of now - x days). I'm somewhat ambivalent on the implementation, and you folks are probably far better than myself to think through the best way to do this. If you'd like me to, I'd be happy to open an issue over in Karpenter if you think that's more appropriate.

from bottlerocket.

There is already a relevant issue opened in Karpenter aws/karpenter-provider-aws#5382, which I think is the right place to solve this, not Bottlerocket SSM params.

from bottlerocket.

I'm fine with that solution as well. May need a separate solution for bottle rocket updater, but we are moving to Karpenter in general.

from bottlerocket.