Sean P. Kelly

As a tip/workaround, one way this can be accomplished would be to use [bootstrap containers](https://github.com/bottlerocket-os/bottlerocket#bootstrap-containers-settings) to add these settings. This would be a lot easier if we had something like...

One "annoying" thing that could happen is that default file sorting (at least on Linux with `ls`) will be a bit unfortunate once we hit `1.10`, since `.` sorts earlier...

Hi @mikkoc. Sorry for the delayed response. We don't currently have a nightly AMI to test, so the easiest way to do the test would be with a Bottlerocket AMI...

I ran out of time to complete this prior to the Bottlerocket 1.8.0 release. We've been discussing ways to use the Prometheus node-exporter to get more data than my simple...

I think rather than rebase the vendored runc fix to previous versions, we can close this issue, since the fix should be available in Kubernetes 1.25 variants and beyond.

Closing this in favor of #2747 for now.

Circling back to this as it's been a while. I think PodDisruptionBudgets captures this use-case. I'll close this issue, but happy to hear use-cases that we're missing if anyone wishes...

Great news for a longstanding issue: EC2 Autoscaling has introduced a capability to use SSM parameters directly in launch templates: * https://aws.amazon.com/about-aws/whats-new/2023/01/amazon-ec2-launch-templates-aws-systems-manager-parameters-amis/ * https://docs.aws.amazon.com/autoscaling/ec2/userguide/using-systems-manager-parameters.html Using this in conjunction with Brupop...

I have confirmed that this works as expected by modifying the launch template of an existing nodegroup in my cluster to use `resolve:ssm:`. I've also opened an [issue against `eksctl`](https://github.com/weaveworks/eksctl/issues/6174)...

@kitsirota thanks for chiming in on that issue. I hadn't tested using managed node groups -- my thinking there was that the AMI launches and lifecycle were intended to be...