-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Multiple NGF Gateways #1443
Comments
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. |
@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. |
Moving milestone to match data and control plane separation. Design should commence during 1.3 development time. |
Moving to 2.0, as the data/control plane separation will be a major release. |
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. |
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
The text was updated successfully, but these errors were encountered: