You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of NGF
I want the control plane to deploy the control plane
So that I do not need to manage it's deployment via Helm
And so that data plane instance management is done by the control plane.
Acceptance
When a Gateway object is created within the cluster and targets NGF as the implementation, the data plane is deployed with the configuration specified via Gateway API.
data plane deployment is configurable via the NginxProxy CRD
the NginxProxy CRD is able to be set at the Gateway level, overriding settings at the GatewayClass level
NginxProxy is currently a cluster-scoped CRD. It will need to become a namespace-scoped CRD (does this require an API version bump?)
If deployment configuration is updated in the NginxProxy resource for a running nginx deployment, then only those fields are updated by NGF. Users should be able to manually update their nginx deployments without being overridden by NGF if those updated fields are not set in the NginxProxy resource.
mpstefan
changed the title
Control Plane Deploys the Data Plane and Remove Data Plane Helm Deployment (single Gateway support)
Deploy the Data Plane with Control Plane
Nov 27, 2024
As a user of NGF
I want the control plane to deploy the control plane
So that I do not need to manage it's deployment via Helm
And so that data plane instance management is done by the control plane.
Acceptance
The text was updated successfully, but these errors were encountered: