J'ai déployé nginx ingress controller avec helm sur mon managed kubernets cloud, le Load Balancer n'acquiert pas d'IP (plus d'une demi heure d'attente).
Logs du pod nginx ingress controller :
```
W0206 12:52:49.607000 7 flags.go:250] SSL certificate chain completion is disabled (--enable-ssl-chain-completion=false)
W0206 12:52:49.607065 7 client_config.go:543] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0206 12:52:49.607317 7 main.go:193] Creating API client for https://10.3.0.1:443
I0206 12:52:49.648559 7 main.go:237] Running in Kubernetes cluster version v1.17 (v1.17.0) - git (clean) commit 70132b0f130acc0bed193d9ba59dd186f0e634cf - platform linux/amd64
I0206 12:52:49.669328 7 main.go:91] Validated default/nginx-ingress-1580993501-default-backend as the default backend.
I0206 12:52:49.789525 7 main.go:102] SSL fake certificate created /etc/ingress-controller/ssl/default-fake-certificate.pem
W0206 12:52:49.904018 7 store.go:636] Unexpected error reading configuration configmap: configmaps "nginx-ingress-1580993501-controller" not found
I0206 12:52:49.929074 7 nginx.go:263] Starting NGINX Ingress controller
I0206 12:52:51.230206 7 nginx.go:307] Starting NGINX process
I0206 12:52:51.231390 7 leaderelection.go:242] attempting to acquire leader lease default/ingress-controller-leader-nginx...
W0206 12:52:51.232688 7 controller.go:394] Service "default/nginx-ingress-1580993501-default-backend" does not have any active Endpoint
I0206 12:52:51.232773 7 controller.go:137] Configuration changes detected, backend reload required.
I0206 12:52:51.273957 7 leaderelection.go:252] successfully acquired lease default/ingress-controller-leader-nginx
I0206 12:52:51.274003 7 status.go:86] new leader elected: nginx-ingress-1580993501-controller-55f7fdcc9-ft9dn
I0206 12:52:51.360416 7 controller.go:153] Backend successfully reloaded.
I0206 12:52:51.360458 7 controller.go:162] Initial sync, sleeping for 1 second.
W0206 12:52:54.819826 7 controller.go:394] Service "default/nginx-ingress-1580993501-default-backend" does not have any active Endpoint
E0206 12:53:13.411645 7 leaderelection.go:367] Failed to update lock: etcdserver: request timed out
E0206 12:54:06.295476 7 leaderelection.go:367] Failed to update lock: etcdserver: request timed out
E0206 13:01:04.510784 7 leaderelection.go:367] Failed to update lock: etcdserver: request timed out
E0206 13:04:50.982010 7 leaderelection.go:367] Failed to update lock: etcdserver: request timed out
E0206 13:17:27.971063 7 leaderelection.go:367] Failed to update lock: etcdserver: request timed out
E0206 13:18:51.144841 7 leaderelection.go:367] Failed to update lock: etcdserver: request timed out
```
Les events du service :
```
Normal EnsuringLoadBalancer 30m service-controller Ensuring load balancer
Normal EnsuringLoadBalancer 28m service-controller Ensuring load balancer
Normal EnsuringLoadBalancer 24m service-controller Ensuring load balancer
Normal EnsuringLoadBalancer 10m service-controller Ensuring load balancer
Normal EnsuringLoadBalancer 3m42s service-controller Ensuring load balancer
```
Il y a quelques jours je parvenais à avoir une IP externe...
Maintenant le LB reste sur pending
Public Cloud OVHcloud - Le Load Balancer d'un nginx ingress controller n'acquiert pas d'IP
Related questions
- Dimensionnement serveur MySQL
45522
07.11.2018 12:32
- [RESOLU] Connexion impossible en SSH
38117
05.06.2019 20:05
- Bonjour, Je n'est reçus aucun mot de passe root lors de mon achat!
33419
05.02.2018 20:47
- Gitlab private docker registry
33126
16.03.2018 13:05
- Ssh connection timed out port 22
32554
11.12.2019 08:21
- Configuration IP failover avec netplan (Ubuntu 17.10)
32048
12.01.2018 23:23
- Problème connexion ssh
31766
04.02.2018 09:46
- IP Failover sur Debian 9
31277
18.11.2016 20:40
- Instance Public Cloud en "error"
28996
15.12.2025 10:04
- Connexion OpenStack Swift Object Storage
25026
11.04.2019 10:09