-
Notifications
You must be signed in to change notification settings - Fork 96
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
Data Plane Dynamic Configuration #929
Comments
The initial version of this should be for supporting tracing configuration. An initial proposal draft was written up here: #931, though was not focused specifically on tracing. https://github.com/nginxinc/nginx-gateway-fabric/blob/main/docs/proposals/control-plane-config.md can also be used as a reference. |
Does the initial proposal need to be updated to include tracing configuration as the first configurable option? The proposal will need to be moved to implementable before design can begin. |
I'd say we can start with tracing. |
Closed as not planned due to our change in strategy for changes in data plane configuration. See #1258 |
Is your enhancement request related to a problem? Please describe.
The NKG data plane will not have a method to manage configuration once the project has a custom nginx container. The NKG project needs a method to configure the data plane outside of the ConfigMap that exists today. Ideally, this configuration should be dynamic and any changes should prompt the data plane to change based on its contents.
What would you like to be added:
A method to dynamically update NKG data plane settings and initial options to configure tracing for NGF and upstream zone size.
Why this is needed:
So users have a method configure the nginx data plane without breaking NKG functionality.
Additional context
Discussion
The text was updated successfully, but these errors were encountered: