-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
bitnami/kubeapps Improved handling of packaging options for Kubeapps #9063
bitnami/kubeapps Improved handling of packaging options for Kubeapps #9063
Conversation
Signed-off-by: Michael Nelson <[email protected]>
Signed-off-by: Michael Nelson <[email protected]>
159d1f5
to
1c04af7
Compare
LGTM! Sorry for not pointing this out in the original PR on Kubeapps, if this is set up:
Installation ends up having Redis but no Flux. I know it might be an edge case, but to avoid this kind of duplicity why not removing the |
Switching this back to draft as I've just noticed an issue with it (we still refer to |
As Antonio pointed out elsewhere, if people create their own plugins, or we work on new plugins, we may want to set the enabledPlugins explicitly. |
Could you merge from master? We just found an issue with the GH action. Sorry for the inconvenience |
Signed-off-by: Michael Nelson <[email protected]>
Signed-off-by: Michael Nelson <[email protected]>
69c0899
to
05296a2
Compare
Merged master and fixed the issue I mentioned earlier (changes from vmware-tanzu/kubeapps#4309 ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! Thanks for the changes, much better UX for enabling the packaging plugins.
Could you check the issues in the actions? It seems that there's missing metadata in the README |
It's a known issue in the readme-generator project, bitnami/readme-generator-for-helm#31 |
Can we merge this, given that the issue for the failing check is known. We don't need to wait for that issue in the readme generator to be fixed to land this (as we similarly landed #8981) |
…itnami#9063) * Improved handling of packaging options for Kubeapps Signed-off-by: Michael Nelson <[email protected]> * Run readme generator. Signed-off-by: Michael Nelson <[email protected]> * Fix other use of redis.enabled from vmware-tanzu/kubeapps#4309 Signed-off-by: Michael Nelson <[email protected]> Signed-off-by: JMSwag <[email protected]>
…itnami#9063) * Improved handling of packaging options for Kubeapps Signed-off-by: Michael Nelson <[email protected]> * Run readme generator. Signed-off-by: Michael Nelson <[email protected]> * Fix other use of redis.enabled from vmware-tanzu/kubeapps#4309 Signed-off-by: Michael Nelson <[email protected]> Signed-off-by: Pavel Sokolov <[email protected]>
Description of the change
This change contains the changes landed in our Kubeapps chart at vmware-tanzu/kubeapps#4265 , but without the update to the plugin paths for now.
Adding Antonio and Rafa as reviewers just to ensure we're on the same page about landing this change now.
Benefits
It gives us a better UX for choosing which packaging system to use with Kubeapps, by allowing the user to choose just the packaging system, while the chart then calculates the required plugins. It also allows the chart to conditionally enable/disable chart dependencies based on the chosen packaging.
Backwards compatible as setting the
kubeappsapis.enabledPlugins
will override (see paste below)Possible drawbacks
I understand the readme-generator-for-helm check failure is known (it doesn't deal with nil values yet), but I'm confused about the
Error: Detected changes in charts without version bump in Chart.yaml. Charts changed: 1 bitnami/kubeapps Version bumps detected: 99
error, given that I have bumped the patch version of the chart?
Applicable issues
Additional information
Here's the output from testing the change by comparing the output of helm template:
Checklist
Chart.yaml
according to semver.