-
Notifications
You must be signed in to change notification settings - Fork 154
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.
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
Add a SIG Scheduling spotlight #519
Comments
/assign @ArvindParekh |
@fsmunoz: GitHub didn't allow me to assign the following users: ArvindParekh. Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
/assign |
Closes: kubernetes#519 Co-authored-by: Arvind Parekh <aruparekh@gmail.com>
Duplicate of #508 :/ Will let the PR close both. |
Closes: kubernetes#519 Co-authored-by: Arvind Parekh <aruparekh@gmail.com>
Closes: kubernetes#519 kubernetes#508 Co-authored-by: Arvind Parekh <aruparekh@gmail.com>
Closes: kubernetes#519 kubernetes#508 Co-authored-by: Arvind Parekh <aruparekh@gmail.com>
We never covered SIG Scheduling and it would be a good addition to the series.
The text was updated successfully, but these errors were encountered: