Closed evanrich closed 2 years ago
@evanrich: This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
nvm
/remove-kind bug
What happened:
I'm not sure if this is a bug or not, but with ingress-nginx deployed, any time I hit a service behind it, the success rate drops below 100%. This is under extremely MILD usage as well, see screenshot:![image](https://user-images.githubusercontent.com/518320/179866233-c78d8a91-e68d-4210-9fa0-1d9a500b64fc.png)
If you look at the non 4xx/5xx (so 200's) graph, it drops as low as 85%:![image](https://user-images.githubusercontent.com/518320/179867495-5cabb547-7225-40f9-b7b6-eff033e2b4d9.png)
What you expected to happen: under low load (<2 rps), it should not drop below 100% success rate
Not sure?
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Kubernetes version (use
kubectl version
): 1.24.1Environment:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release): ubuntu 22.04
Kernel (e.g.
uname -a
): 5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022 x86_64 x86_64 x86_64 GNU/LinuxInstall tools:
kubeadm
Basic cluster related info:
kubectl version
kubectl get nodes -o wide
How was the ingress-nginx-controller installed: helm:
Current State of the controller:
ingress:
How to reproduce this issue:
How to reproduce
install kubernetes install fluxcd deploy helmrelease:
wait for nextcloud to deploy, with ingress, then try hitting endpoint. It doesn't have to be nextcloud, any service I have behind nginx will cause successrate to drop below 100%. Services don't seemm to be impacted either, but the <100% bothers me. deploy ingress