You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
Right now we have configs for kudo controller installation in config/crds and config/default where the second one using kustomize to derive the final yaml from templates. My proposal would be to switch to go templates or whatever helm uses (I think we don't need strategic merge patching here) and introduce kudo init printing out the output yaml.
As a next step, we can easily introduce helm chart for kudo and add it to the main repo.
Why is this needed:
It would simplify kudo installation into cluster a lot.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Right now we have configs for kudo controller installation in
config/crds
andconfig/default
where the second one using kustomize to derive the final yaml from templates. My proposal would be to switch to go templates or whatever helm uses (I think we don't need strategic merge patching here) and introducekudo init
printing out the output yaml.As a next step, we can easily introduce helm chart for kudo and add it to the main repo.
Why is this needed:
It would simplify kudo installation into cluster a lot.
The text was updated successfully, but these errors were encountered: