Cluster tree view - show if gitops is enabled about vscode-gitops-tools HOT 8 CLOSED

@murillodigital I see you added more info to this ticket. Should we close #17?

or do you think we still need to discuss providing Enable GitOps menu option?

from vscode-gitops-tools.

@murillodigital I see you added more info to this ticket. Should we close #17?

or do you think we still need to discuss providing Enable GitOps menu option?

I will provide detail on enabling GitOps in a cluster, which actually will be more than one ticket considering the various paths that could take. In our dev cluster, Flux is already installed - this ticket should also handle the display of Flux was not detected in the cluster for those scenarios. Let me know if that clarifies.

from vscode-gitops-tools.

@murillodigital please provide text tree example of what the above flux check command run should display in our Clusters tree view as child nodes under the sample cluster we are using for testing.

The text code examples you provided above are the results of the command that we will display in Flux terminal output (#48).

The first code sample you provided lists controllers. Do you see Flux as one of the cluster/node components of the cluster? or should that be part of the cluster/node properties view?

Just a reminder this is what our Clusters display now (from #10):

I believe we need to finalize that tree structure similar to what needs to be done for Deployments in #44

This is what I see for namespaces in k8s tools explorer now. That view lists flux-system. Should our Cluster view have the same nodes in our tree, and then list all the controllers under it?

from vscode-gitops-tools.

k8s tools nodes display for reference:

from vscode-gitops-tools.

per our sprint 3 features discussion with @murillodigital each flux enabled cluster should show these controllers child nodes for now:

  helm-controller (version, status)
  image-automation-controller (version, status)
  image-reflector-controller (version, status)
  kustomize-controller (version, status)
  notification-controller (version, status)
  source-controller (version, status)

He doesn't want us to do anything for the Nodes k8s tools explorer displays in this sprint.

@usernamehw see if you can get the list of those nodes and flux system config via kubectl first. I think we'll default to using that k8s tools api and kubectl cli integration when possible before we integrate flux specific commands to keep our gitops extension generic and working with most kubernetes cluster configurations.

from vscode-gitops-tools.

@murillodigital ok. after some minor refactors of that PR, this is what we show for the flux-system deployments in the Clusters tree view:

I think that cluster should list namespaces, flux-system is one of them, and then we should list those controllers under flux-system node which are actually k8s deployments as you see in the editor config.

Now, I find it confusing to see that and separate Deploymets view. Just not very logical or structured in the way k8s clusters are configured with namespaces and deployments, even if we don't include others and just stick with flux k8s object types

from vscode-gitops-tools.

latest cluster view with flux controllers and versions info:

In my opinion, what's missing there is flux-system namespace node that groups those flux controller deployment nodes and shows the info you see in vscode editor pic above.

I'll close this feature ticket as complete for now. It shows if GitOps is enabled and you can also see it in gitops terminal we added in #8 or by running GitOps: Flux Check Prerequisites command I added in #35 any time you want for the currently selected cluster:

from vscode-gitops-tools.

@murillodigital I am closing this as I believe the core functionality for this feature request is implemented.

Please file an enhancements request with a reference to this ticket number, if you feel there is more work that needs to be done for this feature.

from vscode-gitops-tools.