Enable GitOps for existing, not AKS, Kubernetes cluster
See original GitHub issueCreate 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.
Issue Analytics
- State:
- Created 2 years ago
- Comments:12

Top Related StackOverflow Question
@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 installto be executed by the Extension, and then you can manuallyflux uninstallfrom the terminal, making sure you are talking to the right cluster.They do go away.