REQUEST: Netlify site for node-readiness-controller

[Priyankasaggu11929]

Repository

kubernetes-sigs/node-readiness-controller

Project domain

node-readiness-controller.sigs.k8s.io

Additional context for request

No response

[Priyankasaggu11929]

@ajaysundark, creating this issue for us to track the netlify site creation.

Please review/approve the details.

I'll take care of the implementation once it is reviewed/approved. Thanks!

[ajaysundark]

I think we could skip the hyphens for the domain name nodereadinesscontroller.sigs.k8s.io? wdyt?

[Priyankasaggu11929]

Looking at
https://github.com/kubernetes/community/blob/master/github-management/subproject-site-requests.md#requesting-a-netlify-site

and

https://github.com/kubernetes/community/blob/master/github-management/subproject-site-requests.md#requesting-a-subproject-domain

I think we will need to stick to the subproject name

Desired domain name. It should follow the pattern of <sub-project>.sigs.k8s.io and match the request for a subproject domain.

---

I think we could skip the hyphens for the domain name nodereadinesscontroller.sigs.k8s.io? wdyt?

@kubernetes/owners, is it ok to drop hyphens from the subproject name?

[palnabarun]

nodereadinesscontroller.sigs.k8s.io sounds too wordy to me. Adding the hyphens makes it much more readable. (Thoughts aside from the naming policy)

[palnabarun]

Regardless, I think we should stick to the policy, unless there's a very compelling reason to do so.

[ajaysundark]

ack. sounds good. Thanks for your quick feedback!

/lgtm

Regardless, I think we should stick to the policy, unless there's a very compelling reason to do so.

[ajaysundark]

/approve

[Priyankasaggu11929]

/assign