-
Couldn't load subscription status.
- Fork 792
Description
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
node-readiness-controller
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
@dchen1107 , @SergeyKanzhelev , @tallclair , @haircommander , @mrunalp, @ajaysundark
Who should have write access?
@dchen1107 , @SergeyKanzhelev , @tallclair , @haircommander , @mrunalp , @ajaysundark
Who should be listed as approvers in OWNERS?
@dchen1107, @SergeyKanzhelev, @tallclair, @haircommander, @mrunalp, @ajaysundark
Who should be listed in SECURITY_CONTACTS?
@dchen1107, @SergeyKanzhelev, @tallclair, @haircommander, @mrunalp, @ajaysundark
What should the repo description be?
This repository contains a reference implementation of NodeReadinessGates as a Kubernetes controller that manages node taints based on multiple readiness gate conditions, providing fine-grained control over when nodes are ready to accept workloads.
What SIG and subproject does this fall under?
sig-node
Please provide references to appropriate approval for this new repo
This is a sigs sponsored repo for Node Readiness Controller as proposed on 10/7 SIG-Node meeting (agenda)
Additional context for request
No response