Enable GitOps for existing, not AKS, Kubernetes cluster

[RandomFractals]

Create user interface to enable GitOps on an existing cluster already connected to the Kubernetes extension.

From the initial functional spec. by @murillodigital:

The platform operator should be able to enable GitOps in an existing cluster already connected to the Kubernetes extension by clicking a button. A repo should be created and opened as a folder automatically to represent the objects being synchronized with the cluster. The platform operator will be able to see at a glance when the cluster has reached a reconciled state.

As a user, I want to select a non-AKS Kubernetes cluster that does not have Flux installed and have the various Flux components automatically installed in it.

Present the user with a right-click option to "Enable GitOps", only available when the cluster does not have Flux installed (see #36).

The command to execute against the cluster is flux install and should generate output similar to the following:

flux install
✚ generating manifests
✔ manifests build completed
► installing components in flux-system namespace
◎ verifying installation
✔ source-controller: deployment ready
✔ kustomize-controller: deployment ready
✔ helm-controller: deployment ready
✔ notification-controller: deployment ready
✔ install finished

One the install is completed, the cluster should reload and, as per #36, display the version of flux and all its related components.

[murillodigital]

@RandomFractals @usernamehw the development cluster is NOT an AKS cluster, however, since it already has Flux installed, you will not be able to satisfy the condition of the cluster being without it. I'm going to spin a second cluster without Flux, so that you can develop this ticket. We do not want to mess with the flux install on the current cluster cause that would break all the resources already in there. Will provide cluster access details over Slack. The idea here is for flux install to be executed by the Extension, and then you can manually flux uninstall from the terminal, making sure you are talking to the right cluster.

[RandomFractals]

@murillodigital to set up new cluster for us to test this.

[RandomFractals]

@usernamehw please test the config Leo shared in slack once you get flux system nodes and controllers loading done in #36

We should be able to run those flux install/uninstall commands and refresh our Clusters tree view to see extra flux sytem info loaded there.

We'll add the Enable GitOps menu option and command once we can confirm the above manual approach works.

[usernamehw]

@RandomFractals I know that vscode supports passing objects/arrays for setting complex contexts with setContext, but tree view items can only have 1 string context.

Should we use a regex match in package.json and a string context of the type:
|cluster| or |cluster|clusterFluxEnabled| depending on the state
or until we hit the need for 3 contexts on 1 item we can use:
cluster or clusterFluxEnabled depending on the state.

[RandomFractals]

@usernamehw I think we should set cluster node contextValue to fluxCluster when we detect that flux-system namespace from #36 is present and we load those flux controllers.

Then we can simply enable GitOps: Uninstall Flux command for the fluxCluster and enable GitOps: Install Flux command for a regular cluster without flux controllers.

Have you tested the provided cluster without flux as I suggested above?

and do you see flux controllers loaded with that new cluster config when you run flux install and refresh our Clusters tree view?

[usernamehw]

Running flux install...

[RandomFractals]

That looks good. Do you see them go away after you run flux uninstall and refresh the Clusters view?

You can wire those commands if that checks out.

[usernamehw]

They do go away.

[josefaworks]

Make sure ticket #71 is addressed as part of this ticket before closing

[RandomFractals]

@josefaworks This was created originally to enable GitOps on clusters.

We can use #71 to complete the clulsters view refresh story.

@usernamehw please wire enable gitops menu and commands to the tree view first as I described above.

We'll have to handle tree view updates and cluster node status/indicator updates in other places.

[usernamehw]

Not wired to the terminal yet (needs manual refresh), but commands are in place:

[RandomFractals]

this looks good. we'll handle clusters tree view refresh in #71.