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

Umbrella issue for RuntimeClass Scheduling #81016

Closed
7 tasks done
draveness opened this issue Aug 6, 2019 · 6 comments
Closed
7 tasks done

Umbrella issue for RuntimeClass Scheduling #81016

draveness opened this issue Aug 6, 2019 · 6 comments
Assignees
@draveness @tallclair
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@draveness
Copy link
Contributor

draveness commented Aug 6, 2019 •
edited
Loading

The issue works as an umbrella holding up all related items of implementing KEP "RuntimeClass Scheduilng" in 1.16 as a beta feature.

Work Items

Links

/sig node
/sig scheduling
/assign
/cc @tallclair
@draveness draveness added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 6, 2019
@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. labels Aug 6, 2019
@draveness draveness mentioned this issue Aug 7, 2019
Merged
@tallclair tallclair self-assigned this Aug 9, 2019
@tallclair tallclair mentioned this issue Aug 23, 2019
Merged
@draveness draveness mentioned this issue Aug 26, 2019
Merged
@tallclair tallclair mentioned this issue Aug 27, 2019
Closed
@kacole2
Copy link

kacole2 commented Aug 30, 2019

@tallclair @draveness I see #82094 currently in the tide merge pool. However, I do not see #81915 in the merge pool. Is #81915 critical to this being implemented in v1.16? Or since this missed code freeze should this be bumped to v1.17?

@tallclair
Copy link
Member

#81915 is adding tests for functionality that is being added in v1.16. I'm sorry this didn't make code-freeze, but I'd like to see it merged in 1.16.

As a test-only PR, what's the exception request process for this?

@kacole2
Copy link

kacole2 commented Aug 30, 2019

@tallclair file an exception and tag @lachie83 and myself in the email.

@tallclair
Copy link
Member

Exception request filed: https://groups.google.com/d/topic/kubernetes-sig-node/a4WdtrFU8U8/discussion

@draveness
Copy link
Contributor Author

/close

All the PR in this issue have been merged.

@k8s-ci-robot
Copy link
Contributor

@draveness: Closing this issue.

In response to this:

/close

All the PR in this issue have been merged.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@draveness draveness

@tallclair tallclair

Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kacole2 @draveness @k8s-ci-robot @tallclair