Closed pohly closed 1 year ago
/assign @derekwaynecarr
This needs sig-node-leads approval as per this slack conversation: https://kubernetes.slack.com/archives/C01672LSZL0/p1667751787905519
/approve (as sig-node-approver)
/lgtm /approve
I think this needs resolution on https://github.com/kubernetes/kubernetes/pull/111023#issuecomment-1309058680
/approve
repo created: https://github.com/kubernetes/dynamic-resource-allocation PR for branch protection: https://github.com/kubernetes/test-infra/pull/27980 Final step will be completed once PR in k/k is merged.
/assign
The PR has been merged.
Publishing bot also was updated: https://github.com/kubernetes/publishing-bot/pull/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 resource-management
which will absorb the existing noderesourcetopology-api
subproject and include both this new staging repo and the repo that will result from my recent request for a kubernetes-sigs/dra-example-driver
repo.
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: https://github.com/kubernetes/community/pull/6970
With the merging of https://github.com/kubernetes/community/pull/6970, I assume this issue can now be closed?
yup!
/close
@mrbobbytables: Closing this issue.
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)