Closed huiwq1990 closed 1 year ago
Hi @huiwq1990. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: huiwq1990
To complete the pull request process, please assign ravisantoshgudimetla after the PR has been reviewed.
You can assign the PR to them by writing /assign @ravisantoshgudimetla
in a comment when ready.
The full list of commands accepted by this bot can be found here.
Hi @huiwq1990, appreciate the idea here. I am in the middle of combining the cluster-capacity with the descheduler so we can have a component which predicts pod descheduling and their re-scheduling to provide predictions on pod distribution improvements. Implementing a pod generator (or pod injector) is one of the key pieces to be successful. I will be sharing more details later on.
Before we proceed here, I wonder what's your use case for abstracting the pod generator?
Hi @ingvagabund ,recently , I'm looking for a tool which could help me predicate wheather can I shrink some nodes in a k8s cluster. cluster-capacity
is the first one matches my need, but not so much. So I want to use podgenerator to simulate the pods which I want shrink on nodes.
By the way, after investgate I found a similar project open-simulator. Both projects have same mechanism.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
For support multi pods case, extract pod generator.