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

[mchaffee-anaconda]

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?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale