Managing a single Kubernets Ingress with multiple rules

Question

I'm using Kubernetes Ingress on GCP to route traffic to different HTTP services.

TLDR: Is there a way to control a single Ingress object by adding rules to it from multiple different spec files? We want to allow each microservice to deploy it's own routing rules but only have a single (or few) Ingress instance.

Services should be exposed under th Background: One key reason for using Kubernetes to deploy HTTP microservices is our teams can deploy each service independently and even deploy new services without changing any central configuration.

In an environment where there are many (dozens, hundreds?) of HTTP endpoints, each managed and deployed independently, routing becomes an issue; Ingress "should" solve this but we do not want to manage the routing configuration separately or centrally from the services.

Answer 1

There is noway to do control one single Ingress object by adding rules to it from multiple different spec files with GKE Ingress Controller now.

I would say that the GKE Ingress Controller implementation is simply to support you to create K8s Ingress resource with its utilities from the native K8s.

To do something more complex, you need to use other implementations:

• Nginx-ingress controller's "Mergeable Ingress Types Support", like what c4f4t0r recommend.

• Istio ingress gateway, this one I feel it is more simple than Nginx ingress controller. And you can modify your HTTP rules in each Deployment through Virtual Service

For GCP, I would consider using Istio since it is an option when you create cluster now.