From c79c8f2a12c59fd91418ba1e77a30451b88d2610 Mon Sep 17 00:00:00 2001 From: Ritikaa96 Date: Tue, 21 Mar 2023 19:04:20 +0530 Subject: [PATCH] Adding loadbalancerdeprecation info and removing Azure Info in NOTE Signed-off-by: Ritikaa96 --- content/en/docs/concepts/services-networking/service.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 8aa0edf068d..2f97b28f25f 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -654,6 +654,11 @@ You can configure a load balanced Service to [omit](#load-balancer-nodeport-allocation) assigning a node port, provided that the cloud provider implementation supports this. +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. {{< note >}}