Skip to content
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

[Proposal] Adapt Virtual Kubelet providers to KubeZoo's tenant mechanism #36

Open
Tracked by #37
caohe opened this issue Feb 6, 2023 · 0 comments
Open
Tracked by #37
Labels
enhancement New feature or request
Milestone

Comments

@caohe
Copy link
Member

caohe commented Feb 6, 2023

What would you like to be added?

Make Virtual Kubelet aware of the tenant to which a Pod belongs, and create the Pod under the tenant's account and VPC.

Why is this needed?

Public clouds typically provide serverless container services, such as AWS Fargate, Volcano Engine VCI, and Azure ACI. Through the Virtual Kubelet project, a virtual node can be registered in a K8s cluster and connected to these elastic container services.

Therefore, we can adapt Virtual Kubelet providers to KubeZoo's tenant mechanism to achieve data plane isolation between tenants.

@caohe caohe added the enhancement New feature or request label Feb 6, 2023
@caohe caohe added this to the v0.3.0 milestone Feb 6, 2023
@caohe caohe moved this to 📋 Backlog in KubeZoo Development Dashboard Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant