Skip to content
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

settings: figure out how are we doing settings now #10465

Open
lgadban opened this issue Jan 16, 2025 · 0 comments
Open

settings: figure out how are we doing settings now #10465

lgadban opened this issue Jan 16, 2025 · 0 comments

Comments

@lgadban
Copy link
Contributor

lgadban commented Jan 16, 2025

#10458 removes the existing usage of Settings and replaces it with a simple environment variable based solution.

We need to decide the long-term solution for global settings config:

  • is it captured in a CRD?
  • does it dynamically reload the control plane on change?
  • is it actually needed?

Additionally, for the current env var solution, the current flags (as of the linked PR) do not need to be global now that we have truly per-Gateway translation. These flags can be theoretically moved to e.g. GatewayParams so we should analyze that feasibility.

@lgadban lgadban converted this from a draft issue Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant