cloud-provider-azure
cloud-provider-azure copied to clipboard
Introduce a new service annotation to replace service.Spec.LoadBalancerIP
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:
https://github.com/kubernetes-sigs/cloud-provider-azure/issues/1781#tasklist-block-ecb5dc84-8396-45ad-9fd6-b5ed9cd8a154
/assign
what do we have to replace it with ?
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?
I think you are right
Hi @kanha-gupta, do you still plan to do this one?
/assign
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
https://github.com/kubernetes-sigs/cloud-provider-azure/pull/2428 to introduce a new annotation. Use this issue to track as we need to completely remove the service.Spec.LoadBalancerIP in the future.
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
this was added by https://github.com/kubernetes-sigs/cloud-provider-azure/pull/2428.