Introduce a new service annotation to replace service.Spec.LoadBalancerIP

[nilo19]

What would you like to be added:

According to https://github.com/kubernetes/api/blob/master/core/v1/types.go#L4434, we need to introduce a new annotation to replace the loadBalancerIP, as it will be removed in the future.

Why is this needed:

#1781 (comment)

[kanha-gupta]

/assign

[kanha-gupta]

what do we have to replace it with ?

[nilo19]

We can add an annotation here https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/pkg/consts/consts.go
I recommend service.beta.kubernetes.io/azure-load-balancer-ip, what do you think?

[kanha-gupta]

I think you are right

[nilo19]

Hi @kanha-gupta, do you still plan to do this one?

[AfrouzMashayekhi]

/assign

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[nilo19]

#2428 to introduce a new annotation.
Use this issue to track as we need to completely remove the service.Spec.LoadBalancerIP in the future.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[feiskyer]

this was added by #2428.