Update deploy.yaml (#8365)
* Update deploy.yaml Removed the *service.beta.kubernetes.io/exoscale-loadbalancer-name* annotation so it uses service UID by default. It thus removes the current limitation that prevent the installation of several ingress nginx controllers on different clusters belonging to the same organization. * Removing default loadbalancer name
This commit is contained in:
parent
653f1e8a9b
commit
d193c32a70
2 changed files with 0 additions and 2 deletions
|
@ -315,7 +315,6 @@ metadata:
|
|||
annotations:
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-description: NGINX Ingress Controller
|
||||
load balancer
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-name: nginx-ingress-controller
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-service-healthcheck-interval: 10s
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-service-healthcheck-mode: http
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-service-healthcheck-retries: "1"
|
||||
|
|
|
@ -5,7 +5,6 @@ controller:
|
|||
type: LoadBalancer
|
||||
externalTrafficPolicy: Local
|
||||
annotations:
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-name: "nginx-ingress-controller"
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-description: "NGINX Ingress Controller load balancer"
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-service-strategy: "source-hash"
|
||||
service.beta.kubernetes.io/exoscale-loadbalancer-service-healthcheck-mode: "http"
|
||||
|
|
Loading…
Reference in a new issue