John Jeffers

Any suggestions on the correct userdata for EKS Bottlerocket AMIs? Can't use what's suggested above because Bottlerocket doesn't have the `systemd-logind` service.

I opened a support case with AWS about this. You're not allowed to specify `system:*` groups when creating an access entry. I was told it's not currently possible to migrate...

This doesn't allow for arbitrary, non-semver tags. It's an edge case, but if someone uses a custom image tag that isn't semver, the chart will fail. helm template . \...

While we wait for the helm chart for `0.20.0` to be released, is it safe to use the `0.19.0` chart and override `image.tag` to use `0.20.0`? Or are there changes...

It was not answered that I'm aware of and it looks like the chart is still on `0.19.0`. And no shade to anyone. I know this is likely volunteer work...

Are there any plans to address this bug? We are stuck on version 1.4.22 of the controller until this is fixed.

@gthao313 Thank you! Do you have any idea of when this might be fixed? It's costing us several thousand dollars per month to have to run smaller nodes to avoid...

@jackkleeman that sounds to me like standard EC2 limits, not this bug. With the problem I described it was limited to 15 volumes, whereas 24 is about what I would...

@jackkleeman Oh, interesting! I was using r6g.xlarge, which should also have the same limit of 27. We use pod security groups so the ENI trunk for that takes up one...

I vaguely remember that, yeah, but I haven't dealt with it since October, when I switched to smaller instance sizes so we didn't hit the limit, so I can't say...