KusionStack / KusionStack/vscode-kusion

support integration with Azure/AWS/Aliyun clusters, not only minikube

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Feature Request

Describe the feature you'd like:

user story:
I'm using vscode-kusion to test and deploy my apps on Kubernetes on multiple clouds. I want cluster configuration support to easily connect and interact with my clusters.

Once configured the clusters can be viewed as a list and I can choose the current cluster and context to use.

When I trigger kusion apply/destroy/..., the current context will be used.

Furthermore, if I can deploy to a batch of clusters among multiple clouds, It will be nice so that I don't need to repeat the operations on each cluster.

Describe alternatives you've considered:

I've tried setting the k8s config by placing a kubeconfig file at path ~/.kube/config and it worked, but switching between clusters seems tricky. And obviously, that doesn't support batch operation.

Teachability, Documentation, Adoption, Migration Strategy:
documentation about deploying to various clouds is required.

ref

guides on AWS: https://aws.amazon.com/cn/developer/?nc1=f_dr&developer-center-activities-cards.sort-by=item.additionalFields.startDateTime&developer-center-activities-cards.sort-order=asc

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing minikube cluster support and how the extension invokes kusion apply, destroy, and related commands. Define the configuration and context-switching behavior for cloud clusters, then determine how batch operations and cloud deployment documentation should be validated as done.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, azure, kubernetes, typescript
Domain
cloud, devops, devtools, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.