K
Q

Google Cloud Armor/Kubernetes : BackendConfig ignored by ingress

10/25/2018

I created a backend config as described here 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.

I use the nginx ingress controller.

-- gkatzioura
google-cloud-armor
google-cloud-platform
kubernetes

Similar Questions

Use Kubectl Apply command using k8s.io package
How to access internal from external?
How can we use url of datasource in kubernetes while creating configmap
How to provide resource limits in kubernetes go client pod spec?
kubectl get componentstatus Unable to connect to the server: dial tcp xx.xxx.xx.x:xxx: i/o timeout
After deploying Istio bookinfo application on EKS, `kubectl get svc` displays the app's services but `Kubectl get pods` returns `no resources found`
What is the URL to this Kubernetes service/pod/docker thing
Can't connect OKE Kubernetes cluster to Oracle MySQL DB instance that is outside of the cluster

1 Answer

10/29/2018

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

kubectl describe ing

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.

-- gkatzioura
Source: StackOverflow