shadow pod group derives min member from pod annotations #908
Conversation
Hi @mateuszlitwin. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
77dd62e
to
2dd2561
2dd2561
to
8634c1d
/assign @k82cn |
8634c1d
to
88cb8b2
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: k82cn, mateuszlitwin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
What this PR does / why we need it:
Added
scheduling.k8s.io/group-min-member
annotation that allows to specify min member for the shadow pod group.Requiring users to learn new custom resource
PodGroup
and properly handling clean up of such resource is nontrivial and time consuming. In common use case user just want create a batch of pods that will be allocated together at the same time. Extending shadow pod group capabilities could be a solution for this.Which issue(s) this PR fixes:
Fixes #905
Special notes for your reviewer:
Release note: