<p>I created a backend config as described <a href="https://cloud.google.com/kubernetes-engine/docs/how-to/cloud-armor-backendconfig" rel="nofollow noreferrer">here</a> and a cloud armor policy. Then I set the backend config on one of my service's port. It seems that the ingress ignores the BackendConfig.</p>

<p>I use the nginx ingress <a href="https://github.com/kubernetes/ingress-nginx" rel="nofollow noreferrer">controller</a>. </p>

<p>By following the official documentation you might stumble with some issues that have to do with your quota.
You have a limit of 9 backend services by default. The gce configuration in comparison with the nginx-ingress recognises each service exposed through ingress as a backend service.
The best way to troubleshoot it is by issuing</p>

<pre><code>kubectl describe ing
</code></pre>

<p>This will give you the logs needed.
The other issue that needs troubleshooting is when you don't have the correct cluster version which has supports for BackendConfig.</p>
