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

Centralized Configuration #2505

Open
andrewpmartinez opened this issue Oct 28, 2024 · 2 comments
Open

Centralized Configuration #2505

andrewpmartinez opened this issue Oct 28, 2024 · 2 comments
Assignees

Comments

@andrewpmartinez
Copy link
Member

No description provided.

@andrewpmartinez andrewpmartinez converted this from a draft issue Oct 28, 2024
@andrewpmartinez andrewpmartinez self-assigned this Oct 28, 2024
@qrkourier
Copy link
Member

Which configuration could become centralized?

@andrewpmartinez
Copy link
Member Author

Which configuration could become centralized?

The first round are configurations that must/should be the same between controllers.

  • OIDC configuration
  • enrollment durations for routers/identities
  • API rate limiters

Things that won't/can't are host specific configuration or chick-and-egg configurations (i.e. what ports the API is hosted on and its identity).

This effort is controller centric. The future may include router configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Review
Development

No branches or pull requests

2 participants