scheduling framework document updated with permit moved to a scheduling cycle

[mateuszlitwin]

Related PR: kubernetes/kubernetes#88199
Related Issue: kubernetes/kubernetes#88179

[k8s-ci-robot]

Welcome @mateuszlitwin!

It looks like this is your first PR to kubernetes/enhancements 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/enhancements has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mateuszlitwin. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mateuszlitwin
To complete the pull request process, please assign ahg-g
You can assign the PR to them by writing /assign @ahg-g in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• keps/sig-scheduling/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mateuszlitwin]

I do not know how to update the image with scheduling and binding cycle.

[Huang-Wei]

Thanks @mateuszlitwin for working on this. LGTM overall. We need to get the picture updated as well.

Can you also update the "IMPLEMENTATION HISTORY" section?

[Huang-Wei]

@bsalamat @misterikkit (not quite sure you're still getting notified..) By any chance, are you able to share the original editable image in this framework KEP? https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md

[sftim]

/ok-to-test

[mateuszlitwin]

I think the updated picture should show Permit in the scheduling cycle and blue message box with "Wait for a Pod to be approved" text (or something similar) at the beginning of the binding cycle.

[Huang-Wei]

@mateuszlitwin Exactly.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[Huang-Wei]

/remove-lifecycle stale

@mateuszlitwin https://kubernetes.io/docs/concepts/scheduling-eviction/scheduling-framework/ has a picture you can use here to complete this PR.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[misterikkit]

Wei, can you confirm that one of us shared the doc with you back in Feb or May?

…

[Huang-Wei]

Wei, can you confirm that one of us shared the doc with you back in Feb or May?

@misterikkit Yes, I got that from Bobby. Thanks!

BTW: the KEP version is still out-of-dated, but the version on docs.k8s.io is updated.

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[ahg-g]

changes in the PR will be covered in #2054