Gert van den Berg

> > I also have a workaround that requires no bucket permissions / boto3 installation... (S3 redirects to the correct region for a bucket even without permissions, this uses that)...

It seems like a [release was scheduled](https://github.com/kubernetes/autoscaler/pull/8174). The maintainer made [a commit before that day](https://github.com/kubernetes/autoscaler/pull/8237) as well.... I'm not sure if something got forgotten somehow...

> Is 1.32.0 compatible with 1.33.0 or will I see issues if there's a mismatch? It runs and autoscales - it is possible that there might be some edge cases...

There is no release listed on this repo though (I detect the relevant version by fetching all the releases from the github API and looking for the latest cluster-autoscaler that...

> https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.33.0 > > But the latest helm chart is still `1.32.0` You can set the tag with this in you values file: (or `--set image.tag=v1.33.0`) ```yaml image: tag: v1.33.0...

> > > https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.33.0 > > > But the latest helm chart is still `1.32.0` > > > > > > You can set the tag with this in you...

I'm running into something similar with a deployment (when editing labels and selectors....) (Immutable fields on the Deployment in this case, rather than an immutable object) ``` fatal: [localhost]: FAILED!...

Red Hat rebuilt the stream8 container, so rebuilding this one now should help...

CentOS Stream 8 is EoL soon.... (The images likely need to move to CentOS Stream 9 (or something else)) I suspect that the main problem is that Trivy uses the...

.