dschuldt

Great example! Although your php setting _ memory_limit=1536M_ does not make sense since you limit your pod to 1Gi.

We experience the same issue since version 1.8.x. I mentioned it in https://github.com/haproxytech/kubernetes-ingress/issues/460 originally. Since @ivanmatmati asked me to move to this issue, here are my findings summarized: - Restart...

Hi @fabianonunes, we do not deploy the controller with helm but with the plain manifests in the repo. The controller runs with the following args: ``` args: - --configmap=haproxy-controller/haproxy-kubernetes-ingress -...

Hi @ivanmatmati, it does not work with other names or port numbers instead of names either. I also tried with pathType: Prefix for /actuator/health/readiness... it does not work either. So...

Awesome, thanks. Already tested the port rename case successfully. Have a great weekend. Best

@LarsBingBong, the fix landed in v.1.8.2 with this [commit](https://github.com/haproxytech/kubernetes-ingress/commit/9f06093764b9fe5157a91a590b4739469c1e7982). Do you still experience my mentioned issue?

@LarsBingBong, I have not been in office the last days but our developers told me they had to restart the IC several times due to missing servers in haproxy config....

Here is a new observation from today. I changed our haproxy-kubernetes-ingress-default-backend service definition from ``` ... annotations: haproxy.com/backend-config-snippet: | http-request deny deny_status 403 ... ``` to ``` ... annotations: haproxy.com/backend-config-snippet:...

@ivanmatmati, yes it did work afterwards when the IC deployment was restarted. The backend config is valid, it was then written to haproxy.cfg and worked as expected. Sorry for confusion...

@ivanmatmati, I now have a controller deployment with a single pod older than 4 days (no changes have been applied to the cluster during the weekend). Here is what I...