Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cloud provider deprecated in kubelet 1.27+ #10495

Open
YerisAntonio opened this issue Oct 3, 2023 · 9 comments · May be fixed by #11633
Open

cloud provider deprecated in kubelet 1.27+ #10495

YerisAntonio opened this issue Oct 3, 2023 · 9 comments · May be fixed by #11633
Assignees
@tico88612
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@YerisAntonio
Copy link

Hello!

the kubelet option --cloud-provider was deprecated in k8s 1.27. When you configure cloud provider in the inventory, (in my case aws), kubelet crashes "with unknown cloud provide: aws".

I tried adding POC code to kubespray for testing the new way to do this with "--image-credential-provider-bin-dir" and "--image-credential-provider-config" options and it worked fine for me.
@YerisAntonio YerisAntonio added the kind/bug Categorizes issue or PR as related to a bug. label Oct 3, 2023
@yankay
Copy link
Member

yankay commented Oct 7, 2023

@YerisAntonio

Thanks to report it :-)

@yankay yankay added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Oct 7, 2023
@ebarrere
Copy link

ebarrere commented Nov 6, 2023

I also coded an external Cloud Controller Manager to work around this. Not sure which is the "preferred" method, but my changes are here

@taraszka
Copy link

taraszka commented Nov 8, 2023

@ebarrere - does it modify the spec and add spec.providerID?

@VannTen
Copy link
Contributor

VannTen commented Feb 8, 2024

/remove-kind bug
/kind feature
related : #9813

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/bug Categorizes issue or PR as related to a bug. labels Feb 8, 2024
@kkantonop
Copy link

Hello,

I also ran into the same problem trying to provision a cluster with kubespray 2.24.1 (k8s version 1.28).

After reading this thread, I am still puzzled how to progress.
Is there currently a way to deploy k8s version 1.27+ with kubespray in aws?
If so, could you please elaborate?
How can I use the external provider cloud-provider-aws?

Thanks

@ebarrere
Copy link

ebarrere commented Mar 5, 2024

I was able to deploy a cluster using the fork linked in my previous comment, but beyond that I didn't do any testing.

@kkantonop
Copy link

kkantonop commented Jun 5, 2024 •
edited
Loading

Hell all,

I managed to deploy the cluster with kubespray, setting cloud_provider: external.
Then I installed aws-cloud-controller-manager through their helm chart.

To be honest I find that their official documentation is lacking a lot of necessary info, so I ended up troubleshooting from the errors in the logs, the help message of the tool also helped.

docker run --rm registry.k8s.io/provider-aws/cloud-controller-manager:v1.28.1 --help

Cheers!

@tico88612
Copy link
Member

/assign

@tico88612
Copy link
Member

We need to deprecate cloud provider in Kubespray v2.27.

/remove-kind feature
/kind cleanup

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Oct 14, 2024
@tico88612 tico88612 linked a pull request Oct 15, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tico88612 tico88612

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Cleanup: remove in-tree cloud provider support tico88612/kubespray
8 participants
@ebarrere @yankay @taraszka @VannTen @tico88612 @YerisAntonio @k8s-ci-robot @kkantonop