This message was deleted.
# rke2a
adamant-kite-43734
05/19/2025, 8:49 PMThis message was deleted.
c
creamy-pencil-82913
05/19/2025, 8:56 PMIf you’re using the HelmChart suggested there, without a version specified, it’ll deploy whatever the latest version is in that Helm repo.
creamy-pencil-82913
05/19/2025, 8:56 PMhttps://kubernetes.github.io/cloud-provider-aws/index.yaml suggests that 1.27.1 is the latest available
creamy-pencil-82913
05/19/2025, 8:59 PMI don’t see anything newer in the repo. Perhaps AWS has abandoned maintenance of their helm chart?
https://github.com/kubernetes/cloud-provider-aws/blob/master/charts/aws-cloud-controller-manager/Chart.yaml
a
abundant-hair-58573
05/19/2025, 9:14 PMYea it appears so. That's what I gathered as well. There's newer images obviously but the helm version hasn't changed in 2 years
c
creamy-pencil-82913
05/19/2025, 9:17 PMyou might try just changing the image tag to point at a newer version, via chart values?
a
abundant-hair-58573
05/19/2025, 9:17 PMit's possible the old version would have still worked if I wasn't trying to run this in a new air-gapped aws partition that the old aws sdk isn't aware of
abundant-hair-58573
05/19/2025, 9:18 PMyea that's what I did, I just added an image tag in the add-on section of my cluster yaml when provisioning the new cluster
abundant-hair-58573
05/19/2025, 9:20 PMit's still odd that it was ignoring both the custom URL in my cloud.conf and the AWS_EC2_ENDPOINT_URL variable that I set in the controller
12 Views