Comments (12)
@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.
from vscode-gitops-tools.
Running flux install
...
from vscode-gitops-tools.
They do go away.
from vscode-gitops-tools.
@murillodigital to set up new cluster for us to test this.
from vscode-gitops-tools.
@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.
from vscode-gitops-tools.
@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.
from vscode-gitops-tools.
@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?
from vscode-gitops-tools.
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.
from vscode-gitops-tools.
Make sure ticket #71 is addressed as part of this ticket before closing
from vscode-gitops-tools.
@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.
from vscode-gitops-tools.
Not wired to the terminal yet (needs manual refresh), but commands are in place:
from vscode-gitops-tools.
this looks good. we'll handle clusters tree view refresh in #71.
from vscode-gitops-tools.
Related Issues (20)
- Trigger helm chart updates from the UI HOT 10
- Create secret checkbox not working
- Not implemented on AKS/ARC HOT 1
- Prerelease - v0.24.1690210418 reconcile action folds up the treeview HOT 2
- The `flux check` is too aggressive HOT 3
- Performance: still struggles on larger clusters HOT 4
- HelmReleases sometimes pick the wrong API group HOT 1
- Kubectl proxy is run again for multiple extension instances HOT 2
- Release Plan for v0.25.1 patch release
- Editor window can hang on first load HOT 1
- Telemetry collection has been broken since 2-3 weeks ago HOT 5
- Transient states show an error icon HOT 3
- The "Create Source/Kustomization" workflow appears to hang
- Flux binary not found if installed with Brew HOT 2
- Extensions causes lots of kubectl processes to spawn that never finish HOT 10
- Support more Weave GitOps Enterprise features HOT 1
- It's much too easy to accidentally trigger `flux install` HOT 4
- Reorganize and refactor all treeviews HOT 1
- Workload section items overlapping on VScode HOT 11
- different flux namespace HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode-gitops-tools.