Support for Multiple NGF Gateways

[mpstefan]

As a NGF user with a large Kubernetes Cluster
I want to separate my traffic using multiple NGF Gateways
So that I can have separate pieces of infrastructure manage different types of traffic in my environment.

Acceptance

• When the user defines more than one Gateway object in their environment, a corresponding NGF data plane is created.
• If a resource is updated that affects multiple Gateways (or Gateway trees), all corresponding nginx deployments are updated properly.

Dev Notes

• Our current graph assumes one Gateway. It needs to be updated to include a list of Gateways, each containing their configuration tree. The deployment name that is created for each Gateway should be included in its associated Gateway graph so that we know which nginx deployment the configuration belongs to.
• Could be beneficial to draw a diagram to understand how to map resources to their associated Gateways so we know which Gateway tree configurations need to be updated when a resource changes.

[coolbry95]

Would this separate the control and data plane then? This could be a major feature for us as nginx-ingress does not separate the control and data plane leading to us deploying nginx-ingress multiple times per cluster.

[mpstefan]

@coolbry95 It is definitely going to be much easier when they are, and so, yes, we'll be looking at that separation in 1.3 as well.

[mpstefan]

Moving milestone to match data and control plane separation. Design should commence during 1.3 development time.

[mpstefan]

Moving to 2.0, as the data/control plane separation will be a major release.

[vettom]

Another issue I am trying to solve by having multiple Gateway is to separate SSL certificate configuration. With single Gateway certificate/https termination defined in single place, and will have to be managed by central admin team. If Gateway per app, Dev/Projects can define Gateway and their SSL requirements and Certificate manager will provision as required.