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

Observe valuesFrom resources and trigger an update on change #177

Open
duizabojul opened this issue Feb 11, 2023 · 1 comment
Open

Observe valuesFrom resources and trigger an update on change #177

duizabojul opened this issue Feb 11, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@duizabojul
Copy link

What problem are you facing?

I don't know if I use the provider the bad way, but helm release is not updated when I update a config map referenced in valuesFrom. Eventually a refresh will be triggered on a reconcile but it's far from being optimal to wait minutes to get the desired state.

How could Crossplane help solve your problem?

I think the provider should observe resources referenced in valuesFrom and trigger a helm update on change.

@duizabojul duizabojul added the enhancement New feature or request label Feb 11, 2023
@ksawerykarwacki
Copy link

I would suggest against it.

For example, in my current project, we have standard config maps for the whole environment where each key relates to a specific helm chart. We also have XRDs representing instances of our app, which are built from dozens of charts.

If this feature were implemented without any reasonable buffering, any change of the config map would retrigger the reconciliation of hundreds of releases without any need. Observation of specific keys might be better, but we could generate dozens or hundreds of requests besides those created by the reconciliation loop.

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

No branches or pull requests

2 participants