From ede66a1e742d0231ca450594b77ba89c919b8156 Mon Sep 17 00:00:00 2001 From: Ofir Shtrull Date: Mon, 4 Dec 2023 23:52:47 +0200 Subject: [PATCH] Update charts/ingress-nginx/values.yaml Co-authored-by: Marco Ebert --- charts/ingress-nginx/values.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charts/ingress-nginx/values.yaml b/charts/ingress-nginx/values.yaml index eff2bdf85..38d04b44d 100644 --- a/charts/ingress-nginx/values.yaml +++ b/charts/ingress-nginx/values.yaml @@ -525,7 +525,7 @@ controller: # allocateLoadBalancerNodePorts: true # -- Used by cloud providers to connect the resulting internal LoadBalancer to a pre-existing static IP. Make sure to add to the service the needed annotation to specify the subnet which the static IP belongs to. For instance, `networking.gke.io/internal-load-balancer-subnet` for GCP and `service.beta.kubernetes.io/aws-load-balancer-subnets` for AWS. loadBalancerIP: "" - # -- Addes the abilaty to have a diffrnet service type for the internal load balancer + # -- Type of the internal controller service. type: LoadBalancer # -- Restrict access For LoadBalancer service. Defaults to 0.0.0.0/0. loadBalancerSourceRanges: []