weaveworks
Refactor Kustomization Workloads tree view to use flux tree command
Isn't it a bit too early to make this change since flux only supports kustomization but not helm release?
It seems to work (doesn't throw error) if you specify the namespace:
flux tree kustomization kustomization1 -n default
Kustomization/default/kustomization1
Returns only the kustomization itself though. Maybe if the controllers were updated it would print all the resources...
@usernamehw I've update the dev cluster with the latest flux, and I've switched over the sample workloads to a repository suggested by the flux maintainers, which follows a structure that is commonly used by users according to them.
At this moment Kustomizations are fetched by flux tree & Helm Releases (top level) are fetched by kubectl ....
For now the Kustomizations are also loaded in the background, but that will change once Helm Releases also use flux tree (nodes would only load on-demand).
Kustomizations include Helm Releases inside them, so they are kind of duplicated now:
flux tree doesn't include Endpoints & EndpointSlice, not sure if it's important.