Reproduce issue:
Open Cluster Details tab by clicking on disconnected cluster.

Behavior:
Cluster Details tab opens but holds no resources.

Update README.md

Reproduce issue:
Click on the Create Local Environment button, an action container will prompt you to choose between default or custom configuration, press Esc on your keyboard.

Behavior:
Pressing the Esc key at any point during this stage will forcefully create a default or partially configured environment anyway and will not abort/cancel request.

PolicySet CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Manifest work is an essential component of open cluster management.
This feature will help the user to compose a Manifest work CR.
By asking a few questions before generating the CR

Policy Management is an essential component of open cluster management.
This feature will help the user to compose a policy easily CR.
By asking a few questions before generating

• should I place the policy in the policy folder? (if there is no folder, create one)
• Name of the policy
• Type of policy (configuration, IAM ... ) - * the one that OCM supports
• Kind - the resources to apply the policy (pod, service, namespace ... )

steps

• create a kind cluster
• open tree view
• delete the kind cluster
• click on the refresh button

Result: delete cluster should not appear.
Expected: deleted cluster shouldn't appear

Note:
the expected result is relevant mainly for a local Kind cluster.
I am not sure we will be able to achieve that with a remote cluster.

We don't use dependabot and it's been a while since we updated our dependencies.

ManagedClusterSet CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

Templates are saved in our templates directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Templates are a part of our ocmNewProject command, no vscode docs available.
We have multiple templates, each template as its own ManagedClusterSet manifest.

Upgrade resources version for all files under:

https://github.com/open-cluster-management-io/ocm-vscode-extension/blob/4ef114e13e23022503788ee1c7c13885a78690f7/templates/Git

Subscription CRD can be found here.

Snippets are saved in our snippets directory.

Templates are saved in our templates directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Templates are a part of our ocmNewProject command, no vscode docs available.
We have multiple templates, each template as its own Subscription manifest.

Currently, our CI workflows uses Node 16, we need to bump this to he current LTS version, 18.

ClusterClaim CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Updating the snippets and templates technically means updating the versions and validating existing annotations and spec keys based on the updated CRDs.

But I think we're currently missing some spec keys and annotations that might be helpful to users and perhaps worth adding to the snippets and templates, so this all can be part of this task and can be divided to multiple PRs for multiple developers.

We can use this issue to track links to CRDs we're working with and discuss what we want to include in the snippets and templates.

AddOnPlacementScore CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Goal

automate the deployment of the application lifecycle addon by clicking on a button

how

a popup window will ask to pick hub and managed clusters (or just hub. Managed clusters could be selected automatically)
and then trigger a deploy the add-on using the clusteradm

https://open-cluster-management.io/getting-started/integration/app-lifecycle/

We base off cluster names from kubeconfig,
this means that when we deal with clusters configured with a different context and cluster names,
we are unable to connect and get the related resources.

Reproduce issue:
Open Cluster Details tab, move to a different tab, move back to Cluster Details tab.

Behavior:
Cluster Details tab is no longer connected to any one cluster and holds no resources, screen is blank and is not reactive.

While trying to install the extension, VSCode shows that
The 'OCM Extension' extension is not available in Visual Studio Code for Mac Silicon. Learn More

Channel CRD can be found here.

Snippets are saved in our snippets directory.

Templates are saved in our templates directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Templates are a part of our ocmNewProject command, no vscode docs available.
We have multiple templates, each template as its own Channel manifest.

Placement CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

Templates are saved in our templates directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Templates are a part of our ocmNewProject command, no vscode docs available.
We have multiple templates, each template as its own Placement manifest.

Business case

User would like to mark managed clusters differently based on type or location e.g Dev/Prod
and show those labels in the web UI

proposal

Enable the option to add labels to managed clusters from UI.

We need to add tests.
Currently, we barely scratch the 54% coverage ratio, we should for 75-90.

Policy CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

PlacementBinding CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Add the ApplicationSet snippets which include OCM specific annotation for the following features:

• Argocd integration
• Argocd pull integration

when right-clicking on cluster opens a web view with the basic status of the existing subscription.
using pattern fly: https://www.patternfly.org/v4/get-started/develop/

TBD - fields to show up

Currently we run tests that access vscode as integration tests inside vscode-electron's sandbox using mocha.

Tests that do not require vscode, run as standard unit tests with mocha.

After recent features and modifications, keeping this separation doesn't make sense anymore.
We need to run all tests from within the sandbox.

PlacementRule CRD can be found here.

Snippets are saved in our snippets directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Early access released are created and as draft instead of pre-releases and aren't stacked up instead of being replaced.

ManagedClusterSetBinding CRD can be found here.

Snippets are saved in our snippets directory.

Templates are saved in our templates directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21

Templates are a part of our ocmNewProject command, no vscode docs available.
We have multiple templates, each template as its own ManagedClusterSetBinding manifest.

Current feature

the Create local environment button is deploying OCM on local kind clusters

Suggested

support bootstrapping both local and remote env

• Change the button name to Create environment or Bootstrap OCM (instead of the current Create local environment)
• After clicking, users will be asked: Create new clusters using Kind?
  • Yes, we go on exactly like we do today.
  • No, we'll present a list of the current contexts from kubeconfig. Users will select one context for the hub and one-to-many contexts for the spokes.

Note:
We already decided that we won't offer kubeconfig contexts management. OCM extension relies on existing mechanism

by triggering clusteradm commands from VS code
allowing the creation of a new cluster, joining managed clusters, updating clusters, and more.

Manifestwork CRD can be found here.

Resource docs can be found here.

Snippets are saved in our snippets directory.

VSCode Snippet Guide.
VSCode Using Snippets.

Related issue: #21