-
Notifications
You must be signed in to change notification settings - Fork 687
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
new staging repo: k8s.io/dynamic-resource-allocation #3821
Comments
/assign @derekwaynecarr This needs sig-node-leads approval as per this slack conversation: |
/approve (as sig-node-approver) |
/lgtm |
I think this needs resolution on kubernetes/kubernetes#111023 (comment) |
This is needed for helper code for the dynamic resource allocation feature. The code will be added in kubernetes/kubernetes#111023 The repo request is in kubernetes/org#3821
/approve |
repo created: https://github.com/kubernetes/dynamic-resource-allocation /assign |
The PR has been merged. Publishing bot also was updated: kubernetes/publishing-bot#300 |
I think everything is done as far as getting the repo squared away. The only administrative action left is to add it to k/community listed under a subproject Would it be a new one or should it be listed under one of the others? |
Let me ask what people prefer in the sig-node meeting today. |
We discussed this in the sig-node meeting on Tuesday. The consensus was for me to create a new subproject called The first step is to open a PR against https://github.com/kubernetes/community to update the README with the new organization. What are the following steps? It looks like maybe an update to https://github.com/kubernetes/community/blob/master/sigs.yaml as well? Anything else? |
PR to add the above: |
With the merging of kubernetes/community#6970, I assume this issue can now be closed? |
yup! /close |
@mrbobbytables: Closing this issue. 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/test-infra repository. |
From https://groups.google.com/g/kubernetes-sig-architecture/c/DkKQyuUrj9Y:
There have been no comments there, so I suppose there are no objections and we can proceed.
/cc @thockin (in case that explicit approval is needed)
The text was updated successfully, but these errors were encountered: