bottlerocket-os / bottlerocket-os/bottlerocket
vmware images are using a removed argument for api-server cloud-provider=external
- Dominant language
- Rust
- Stars
- 9.7k
- Forks
- 586
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
**Image I'm using:**
bottlerocket-v1.33.5-kubernetes-1-33-eks-17-amd64-a5ca614
**What I expected to happen:**
(EKSA) Update to go as expected, with all services starting
**What actually happened:**
Found node wouldn't become ready, looked at the pods and found an error in the logs:
```
macintoshme@werk ~ k logs kube-apiserver-dvlp-workload-bdb7h
Error: unknown flag: --cloud-provider
```
**How to reproduce the problem:**
I am very surprised no one else has run into this as it appears to affect all vmware 1.33 clusters:
Found what appears to be the offending lines:
https://github.com/bottlerocket-os/bottlerocket/blob/79b1eceaaf819c19ad906d460824a4325f935205/sources/shared-defaults/kubernetes-vmware.toml#L7
https://github.com/bottlerocket-os/bottlerocket/blob/79b1eceaaf819c19ad906d460824a4325f935205/sources/shared-defaults/kubernetes-aws-external-cloud-provider.toml#L2
This was [removed in 1.31](https://kubernetes.io/blog/2024/08/13/kubernetes-v1-31-release/#removal-of-all-in-tree-integrations-with-cloud-providers), but I think it wasn't an issue until they actually [removed it from kubernetes later](https://github.com/kubernetes/kubernetes/pull/130162/files).
Contributor guide
Assessment
This issue has not been assessed yet.