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

Virtual Kubelet: ClusterSet Integration #121

Open
Tracked by #124
MbolotSuse opened this issue Oct 1, 2024 · 2 comments
Open
Tracked by #124

Virtual Kubelet: ClusterSet Integration #121

MbolotSuse opened this issue Oct 1, 2024 · 2 comments
Assignees
Labels
priority/1 virtual-kubelet all virtual kubelet related issues

Comments

@MbolotSuse
Copy link
Contributor

MbolotSuse commented Oct 1, 2024

A review should be done to make sure that the virtual kubelet implementation integrates well with the ClusterSet. Specifically, the following features should be integrated/implemented/tested:

  • The cluster set should be able to provide a network policy preventing clusters from accessing a cluster in another cluster set
  • The cluster set should be able to specify a PSS that applies to every pod in every virtual cluster in the set
  • The cluster set should be able to specify a priority class that applies to every pod in every virtual cluster in the set
  • The cluster set's resource limits and defaults should apply to all workloads in every virtual cluster in the set
  • Only workloads which are currently running should apply to the limits set in the cluster set
  • The cluster set should specify which node type (shared vs virtual) is allowed
@jp-gouin
Copy link
Collaborator

Can we close this one ?

@jp-gouin jp-gouin added the priority/0 high priority label Dec 24, 2024
@enrichman
Copy link
Collaborator

Not yet, some of the bullet points still needs to be implemented:

  • The cluster set should be able to provide a network policy preventing clusters from accessing a cluster in another cluster set
  • The cluster set should be able to specify a PSS that applies to every pod in every virtual cluster in the set
  • The cluster set should be able to specify a priority class that applies to every pod in every virtual cluster in the set
  • The cluster set's resource limits and defaults should apply to all workloads in every virtual cluster in the set
  • Only workloads which are currently running should apply to the limits set in the cluster set
  • The cluster set should specify which node type (shared vs virtual) is allowed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/1 virtual-kubelet all virtual kubelet related issues
Projects
None yet
Development

No branches or pull requests

4 participants