[go: up one dir, main page]

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

Graceful handling of Helm repository management features for the HA setup #3429

Open
pepov opened this issue Feb 10, 2021 · 0 comments
Open
Labels

Comments

@pepov
Copy link
Contributor
pepov commented Feb 10, 2021

Is your feature request related to a problem? Please describe.
Helm repository management features like adding, removing or updating repositories do not work in HA setup. The node that gets the request can only perform the required repo management action locally on its own filesystem. Unfortunately there is no way to use another backend (like a database) that would work in a HA scenario seamlessly.

Describe the solution you'd like to see
I would like to disable repo management options in a HA scenario for the short term until figure out whether we want to keep it around in the long term or not.

Approach:

  • create a configuration flag that would disable the API endpoints in question (or make them raise an error if called)
  • add a feature flag for clients to understand that the repo management features are disabled

Describe alternatives you've considered
We've considered creating proxy endpoints that would know about all the running pipeline instances and would fanout an incoming request to all backends. We are hesitant to implement it until we get feedback on whether anybody uses this combination or not (HA + Helm repo management features)

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

No branches or pull requests

2 participants