Skip to content

Support for Multiple NGF Gateways #1443

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

Closed
mpstefan opened this issue Jan 4, 2024 · 9 comments
Closed

Support for Multiple NGF Gateways #1443

mpstefan opened this issue Jan 4, 2024 · 9 comments
Assignees
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/extra-large
Milestone

Comments

@mpstefan
Copy link
Member

mpstefan commented Jan 4, 2024

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.
@mpstefan mpstefan added this to the v1.3.0 milestone Jan 4, 2024
@coolbry95
Copy link

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
Copy link
Member Author

@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
Copy link
Member Author

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

@mpstefan mpstefan modified the milestones: v1.4.0, v2.0.0 Jun 4, 2024
@mpstefan
Copy link
Member Author

mpstefan commented Jun 4, 2024

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

@vettom
Copy link

vettom commented Jul 12, 2024

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.

@mpstefan mpstefan modified the milestones: v1.5.0, v2.0.0 Aug 5, 2024
@mpstefan mpstefan modified the milestones: v1.6.0, v2.0.0 Nov 18, 2024
@sjberman sjberman added enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/extra-large labels Jan 27, 2025
@omegion
Copy link

omegion commented Feb 7, 2025

Any progress on supporting multiple Gateways?

@mpstefan
Copy link
Member Author

Hey @omegion! Quite a bit in fact, although we know this is going to be a big effort. We're still planning on having this in our end of March release as part of our new separate data and control plane architecture.

@sjberman
Copy link
Collaborator

We're likely looking at the 2.0 release being out a bit after March at this point, there's a lot of work going into the new architecture. But we are making steady progress, which can be followed in #1508.

@sindhushiv sindhushiv moved this from 🏗 In Progress to 🆕 New in NGINX Gateway Fabric Mar 13, 2025
@salonichf5 salonichf5 moved this from 🆕 New to 🏗 In Progress in NGINX Gateway Fabric Mar 14, 2025
@sjberman sjberman moved this from 🏗 In Progress to 👀 In Review in NGINX Gateway Fabric Apr 14, 2025
@sindhushiv sindhushiv moved this from 👀 In Review to ✅ Done in NGINX Gateway Fabric Apr 21, 2025
@sindhushiv sindhushiv closed this as completed by moving to ✅ Done in NGINX Gateway Fabric Apr 21, 2025
@sjberman sjberman reopened this Apr 21, 2025
@github-project-automation github-project-automation bot moved this from ✅ Done to 🆕 New in NGINX Gateway Fabric Apr 21, 2025
@sjberman sjberman moved this from 🆕 New to 👀 In Review in NGINX Gateway Fabric Apr 21, 2025
@sjberman sjberman moved this from 👀 In Review to ✅ Done in NGINX Gateway Fabric Apr 22, 2025
@sjberman sjberman closed this as completed by moving to ✅ Done in NGINX Gateway Fabric Apr 22, 2025
@sjberman
Copy link
Collaborator

This work has been implemented and is currently living in a feature branch. It will be released with 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/extra-large
Projects
Status: Done
Development

No branches or pull requests

7 participants