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.

Sign up for GitHub

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

Jump to bottom

Add operator to manage controller in cluster #1122

Open
wzshiming opened this issue May 29, 2024 · 4 comments · May be fixed by #1189
Open

Add operator to manage controller in cluster #1122

wzshiming opened this issue May 29, 2024 · 4 comments · May be fixed by #1189
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
v0.7

Comments

@wzshiming
Copy link
Member

What would you like to be added?

We need to manage the deployment of the controller in various configurations to maintain an optimal ratio of controllers to nodes in the cluster.

  • One-to-Many (1:M) Relationship: In this configuration, a single controller is responsible for managing all.
  • Many-to-Many (N:M, N<M) Relationship: This configuration is used when there are a large number of nodes. Due to limitations in heartbeat and apiserver QPS, a single controller may not be able to maintain too many nodes. Currently, it is recommended for a controller to maintain up to 1000 nodes.
  • Many-to-Many (N:M, N=M) Relationship: In this configuration, the number of controllers is equal to the number of nodes. This is used to simulate the pressure of the same kubelet on the apiserver.

In a Many-to-Many, there may be a need to assign a distinct controller for the management of resources that are not contained within a node or pod.
It’s important to note that managing these resources is not limited to a single controller, as they may also have requirements that necessitate management by multiple controllers.

Why is this needed?

From discussion https://kubernetes.slack.com/archives/C04RG2YSK16/p1716796734402529
@wzshiming wzshiming added the kind/feature Categorizes issue or PR as related to a new feature. label May 29, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in KWOK Tracking May 29, 2024
@wzshiming wzshiming added this to the v0.7 milestone May 29, 2024
This was referenced Jun 6, 2024
Closed
Closed
@wzshiming wzshiming mentioned this issue Jul 1, 2024
Open
@wzshiming wzshiming linked a pull request Jul 31, 2024 that will close this issue
Open
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 27, 2024
@wzshiming wzshiming mentioned this issue Sep 2, 2024
Open
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 26, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2024
@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in KWOK Tracking Oct 26, 2024
@wzshiming wzshiming reopened this Oct 27, 2024
@github-project-automation github-project-automation bot moved this from ✅ Done to 📋 Backlog in KWOK Tracking Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
KWOK Tracking
Status: 📋 Backlog
Milestone
v0.7
Development

Successfully merging a pull request may close this issue.

[WIP] Add kwok operator wzshiming/kwok
3 participants
@wzshiming @k8s-ci-robot @k8s-triage-robot