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.

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

Docs discourage changing aws-load-balancer-type, which is required to migrate from CCM #4000

Open
mchaffee-anaconda opened this issue Jan 6, 2025 · 0 comments

Comments

@mchaffee-anaconda
Copy link

mchaffee-anaconda commented Jan 6, 2025

Is your feature request related to a problem?
I have a Service of type: LoadBalancer which is currently controlled by the in-tree cloud-controller-manager (CCM) because I have set service.beta.kubernetes.io/aws-load-balancer-type: nlb.

I need to migrate this Service to using the AWS LBC instead, which requires me to change aws-load-balancer-type. But the docs say this:

It's not recommended to modify or add the service.beta.kubernetes.io/aws-load-balancer-type annotation on an existing Service resource. If a change is desired, delete the existing Service resource and create a new one instead of modifying an existing Service.

Deleting and recreating the Service is not a good option since that would require several minutes of unnecessary downtime as DNS changes propagate.

Describe the solution you'd like

Is that line in the documentation discouraging changing back to using the CCM? Or does it also discourage in-place migration from CCM to LBC?

Is in-place migration from CCM to LBC possible without having to delete the Service?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants