dschuldt

Hi @ivanmatmati, now I have something: ``` 2022/07/18 09:12:19 ERROR ingress/ingress.go:245 Ingress 'spot-e2etest-login-service-12337/wiremock': service 'spot-e2etest-login-service-12337/wiremock' does not exist 2022/07/18 09:12:19 ERROR ingress/ingress.go:245 Ingress 'spot-e2etest-login-service-12337/spot-login': service 'spot-e2etest-login-service-12337/spot-login' does not exist 2022/07/18...

We now use the Helm chart and set a proper ingressclass. Still the issue occurs. I now believe it's related to store.go (lines 186-189) ``` svc, svcOk := ns.Services[name] if...

I wonder if this is related to https://github.com/haproxytech/kubernetes-ingress/issues/312

Here is some interesting information I could gather today. In a cluster without frequent deployments/config changes, this is the RAM consumption before and after a restart. The IC was running...

@pnmatich you could try with this command. We are using it for our HAProxy (not as Ingress though): ``` lifecycle: preStop: exec: command: ["/bin/sh","-c","sleep 10; kill -SIGUSR1 $(pidof haproxy)"] ```...

I tried myself with our ingress controller setup; I experience the same issues. Neither ``` command: ["/bin/sh","-c","sleep 10; kill -SIGUSR1 $(pidof haproxy)"] ``` nor ``` command: ["/bin/sh","-c","s6-svc -1 /var/run/s6/services/haproxy"] ```...

Please do not close this issue, stale.