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.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
NGINX Ingress controller version:
0.19.0
Kubernetes version (use kubectl version):
v1.11.1
Environment:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
What happened:
before apply the change of nginx, the nginx ingress controller have logic to generate a tmp file which used for nginx test with nginx -t, so if some ingress resource have bad configuration to failed pass the test, the tem file will not have change to delete, so it will generate so many tmp file like below:
root@nginx-ingress-controller-lqd4j:/tmp# ls -lrt | grep nginx-cfg | wc -l
4952
from above info, we can see that have about 5000 files generated.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
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/.):
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.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
NGINX Ingress controller version:
0.19.0
Kubernetes version (use
kubectl version
):v1.11.1
Environment:
uname -a
):What happened:
before apply the change of nginx, the nginx ingress controller have logic to generate a tmp file which used for nginx test with
nginx -t
, so if some ingress resource have bad configuration to failed pass the test, the tem file will not have change to delete, so it will generate so many tmp file like below:from above info, we can see that have about 5000 files generated.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: