Create Cluster Deployments tree view about vscode-gitops-tools HOT 7 CLOSED

@RandomFractals @usernamehw I have added the missing objects to the cluster - please go ahead with HelmRelease integration that I think is the one thing pending to close this ticket. I have additional spec to document as to further behavior with nested nodes within each of these objects but will detail that separately.

from vscode-gitops-tools.

1. What commands do we need to run, or repo/cluster source config files to load and interpret to display the list of available Deployments?

kubectl get Kustomization -A
kubectl get HelmRelease -A

Note that the -A flag mean "all namespaces", although not quite speced out yet, it is likely we will need to enable some form of namespace specific grouping (likely by, as a sub-element of the clusters tree, allow for the selection of a namespace), when such filtering is in place, the commands would be:

kubectl get Kustomization -n {namespace}
kubectl get HelmRelease -n {namespace}

Also consider that the output of the command above is not ideal for parsing, adding -o json or -o yaml to either will output much more detailed information in a parseable way.

from vscode-gitops-tools.

Kustomization & HelmRelease from all namespaces are listed in tree view:

from vscode-gitops-tools.

@murillodigital I will need more information on what is displayed in this Deployments tree view "at a glance".

Questions:

1. What commands do we need to run, or repo/cluster source config files to load and interpret to display the list of available Deployments?
2. What UI menu options should be added for Deployments at the view and individual node levels?
3. Is Deployments just a list of deployed apps, and does it have nested nodes structure? What is the full hierarchy of the Deployments tree view? Please provide more extensive tree structure examples in text, if it's more than just a list.
4. Do we expose standard vscode Refresh option on Deployments or reload them based on other actions performed by gitops ext.? What does that include? Config file changes, some wego/flux commands run by the Cloud Operator?

from vscode-gitops-tools.

2\. What UI menu options should be added for Deployments at the view and individual node levels?

3\. Is Deployments just a list of deployed apps, and does it have nested nodes structure? What is the full hierarchy of the Deployments tree view? Please provide more extensive tree structure examples in text, if it's more than just a list.

For now, none, I suggest we populate the top level and then iterate. Do consider that there most likely will be options and sub-levels, so make sure the code is written in a way that such implementation is possible with little impact, but at this point I think we want to get to populated high level tree views and then we can go into specific, more in-depth behavior in further iterations.

Are these imminent decisions that must be made at this stage that have hard consequences going forward?

from vscode-gitops-tools.

4\. Do we expose standard vscode Refresh option on Deployments or reload them based on other actions performed by gitops ext.? What does that include? Config file changes, some `wego`/`flux` commands run by the Cloud Operator?

Let's talk more about this, as there are multiple paths to reload, some of them event driven from the Kubernetes side, which is an issue we will encounter in multiple node "types". Eg. If a manual change was performed in the cluster, and a Kustomization object has detected that drift, and automated reconciliation process will be triggered, which ideally should be visible in the user interface, but that event occurred entirely "within the cluster", not by any action initiated nor predictable on the VS Code side.

from vscode-gitops-tools.

top level gitops views:

from vscode-gitops-tools.