You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
pem, certificate, remove, stuck, delete, tls, secret
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
NGINX Ingress controller version: 0.20.0
Kubernetes version (use kubectl version): v1.10.10
Environment:
Cloud provider or hardware configuration: hardware
OS (e.g. from /etc/os-release): 16.04.5 LTS (Xenial Xerus)
Kernel (e.g. uname -a): Linux prod-kube-master 4.15.0-47-generic Ingress only exposes internal node ip #50~16.04.1-Ubuntu SMP Fri Mar 15 16:06:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Install tools:
Others:
What happened:
After remove tls section from ingress object. Pem file remains in the container. And prometheus metric nginx_ingress_controller_ssl_expire_time_seconds indicates that the certificate has expired. But no secret in kubernetes cluster.
What you expected to happen: After deleting the secret and deleting tls section from the ingress object, the file must also be removed from the container.
How to reproduce it (as minimally and precisely as possible):
Create a secret with a certificate and ingress that uses it:
Let's look at the files in the controller container:
www-data@kube-master:/etc/nginx$ ls -lah /etc/ingress-controller/ssl/kube-system*
-rw-r--r-- 1 www-data www-data 887 May 15 10:57 /etc/ingress-controller/ssl/kube-system-ingress-tls-full-chain.pem
-rw------- 1 www-data www-data 1.1K May 15 10:57 /etc/ingress-controller/ssl/kube-system-ingress-tls.pem
After deleting pod with controller:
www-data@kube-master:/etc/nginx$ ls -lah /etc/ingress-controller/ssl/kube-system*
ls: cannot access '/etc/ingress-controller/ssl/kube-system*': No such file or directory
The text was updated successfully, but these errors were encountered:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
No
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
pem, certificate, remove, stuck, delete, tls, secret
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
NGINX Ingress controller version: 0.20.0
Kubernetes version (use
kubectl version
): v1.10.10Environment:
uname -a
): Linux prod-kube-master 4.15.0-47-generic Ingress only exposes internal node ip #50~16.04.1-Ubuntu SMP Fri Mar 15 16:06:21 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxWhat happened:
After remove tls section from ingress object. Pem file remains in the container. And prometheus metric
nginx_ingress_controller_ssl_expire_time_seconds
indicates that the certificate has expired. But no secret in kubernetes cluster.What you expected to happen: After deleting the secret and deleting tls section from the ingress object, the file must also be removed from the container.
How to reproduce it (as minimally and precisely as possible):
Create a secret with a certificate and ingress that uses it:
Remove the certificate and remove the tls section from the ingress:
Let's look at the files in the controller container:
After deleting pod with controller:
The text was updated successfully, but these errors were encountered: