-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable GitOps for existing, not AKS, Kubernetes cluster #17
Comments
@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 |
@murillodigital to set up new cluster for us to test this. |
@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 We'll add the |
@RandomFractals I know that vscode supports passing objects/arrays for setting complex contexts with Should we use a regex match in |
@usernamehw I think we should set cluster node Then we can simply enable Have you tested the provided cluster without and do you see |
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. |
They do go away. |
Make sure ticket #71 is addressed as part of this ticket before closing |
@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. |
Please don't use it on the good/populated `default` cluster
this looks good. we'll handle clusters tree view refresh in #71. |
Create user interface to enable GitOps on an existing cluster already connected to the Kubernetes extension.
From the initial functional spec. by @murillodigital:
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.
The text was updated successfully, but these errors were encountered: