Change:
This is a Bug Report Problem: As per , the has been deprecated since 1.24 but the docs does not mention about the deprecation - Proposed Solution: should mention the deprecation at least. Page to Update:
/triage accepted
Hi , the triage has been accepted and if you want to contribute the change you can assign it to yourself . If not, please let us know here, I'll be happy to add this
Thank you. Please go ahead
Great . Thanks /assign
/sig apps /sig network /sig docs
Continuing the discussion for change: One way we can apply this change is by adding a note: But should we give an example of the annotations ?
Hi , Raised a PR for the Note:

Discussion:
Traffic from the external load balancer is directed at the backend Pods. The cloud provider decides how it is load balanced. <del> Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified, the loadBalancer is set up with an ephemeral IP address. If you specify a `loadBalancerIP` but your cloud provider does not support the feature, the `loadbalancerIP` field that you set is ignored. </del> To implement a Service of `type: LoadBalancer`, Kubernetes typically starts off by making the changes that are equivalent to you requesting a Service of `type: NodePort`. The cloud-controller-manager component then configures the external load balancer to

[omit](#load-balancer-nodeport-allocation) assigning a node port, provided that the cloud provider implementation supports this. <ins> Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified, the loadBalancer is set up with an ephemeral IP address. If you specify a `loadBalancerIP` but your cloud provider does not support the feature, the `loadbalancerIP` field that you set is ignored. </ins> {{< note >}} <del> On **Azure**, if you want to use a user-specified public type `loadBalancerIP`, you first need to create a static type public IP address resource. This public IP address resource should be in the same resource group of the other automatically created resources of the cluster. For example, `MC_myResourceGroup_myAKSCluster_eastus`. Specify the assigned IP address as loadBalancerIP. Ensure that you have updated the `securityGroupName` in the cloud provider configuration file. For information about troubleshooting `CreatingLoadBalancerFailed` permission issues see, [Use a static IP address with the Azure Kubernetes Service (AKS) load balancer](https://docs.microsoft.com/en-us/azure/aks/static-ip) or [CreatingLoadBalancerFailed on AKS cluster with advanced networking](https://github.com/Azure/AKS/issues/357). </del> <ins> The`.spec.loadBalancerIP` field for a Service was deprecated in Kubernetes v1.24. This field was under-specified and its meaning varies across implementations. It also cannot support dual-stack networking. This field may be removed in a future API version. If you're integrating with a provider that supports specifying the load balancer IP address(es) for a Service via a (provider specific) annotation, you should switch to doing that. If you are writing code for a load balancer integration with Kubernetes, avoid using this field. You can integrate with [Gateway](https://gateway-api.sigs.k8s.io/) rather than Service, or you can define your own (provider specific) annotations on the Service that specify the equivalent detail. </ins> {{< /note >}}