Conversation
Signed-off-by: Swati Gupta <swatig@nvidia.com>
github-project-automation
bot
moved this to Backlog
in Planning Board: k8s-dra-driver-gpu
guptaNswati
moved this from Backlog
to In Progress
in Planning Board: k8s-dra-driver-gpu
guptaNswati
added
documentation
There was a problem hiding this comment.
Pull request overview
Adds a formal policy document describing how feature gates in the NVIDIA DRA Driver for GPUs should progress from Alpha to Beta to Stable, including evidence expectations and a snapshot of the current gate inventory.
Changes:
- Introduces graduation criteria (entry/graduation requirements) for Alpha, Beta, and Stable feature gates.
- Defines deprecation/removal expectations and upstream Kubernetes dependency coupling rules.
- Documents current feature-gate inventory and highlights gaps to reach/maintain desired stages.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### 2.3 Stable (GA) — Production Grade | ||
|
|
||
| **Default:** `true`, **Locked:** feature gate cannot be disabled |
| | `DynamicMIG` | Alpha | `false` | v25.12 | [KEP-4815] (Alpha 1.35, Beta target 1.36) | Mutually exclusive with PassthroughSupport, NVMLDeviceHealthCheck, MPSSupport | | ||
| | `NVMLDeviceHealthCheck` | Alpha | `false` | v25.12 | [KEP-5055] (Alpha 1.33, Beta target 1.36) | Mutually exclusive with DynamicMIG | |
| @@ -0,0 +1,184 @@ | |||
| # Policy on Feature Gate Graduation | |||
| **Default:** `false` (opt-in) | ||
| **Signal:** "Try it out and give us feedback." |
| **Default:** `true` (opt-out) | ||
| **Signal:** "We're confident in the design. Early production use is | ||
| encouraged." |
| When the upstream dependency is not at the required level, the feature must | ||
| detect and degrade gracefully, require and fail loudly, or defer promotion. | ||
|
|
||
| ## 3. Current Feature Gate Inventory |
There was a problem hiding this comment.
I think its better to make this doc just about policy and adding the details of current feature gates on a different doc.
Even better would be that each feature gate has a dedicated page with details about it.
There was a problem hiding this comment.
Thats a good idea. Rn, we dont have any doc on the FGs. A dedicated page would allow us to have design, discussions and different stages at a single place.
There was a problem hiding this comment.
Yes. We should at least split the static policy section and the dynamic feature gate section.
rajatchopra
left a comment
rajatchopra
left a comment
There was a problem hiding this comment.
How do we reconcile information here with roadmap/issues?
| When the upstream dependency is not at the required level, the feature must | ||
| detect and degrade gracefully, require and fail loudly, or defer promotion. | ||
|
|
||
| ## 3. Current Feature Gate Inventory |
There was a problem hiding this comment.
Yes. We should at least split the static policy section and the dynamic feature gate section.
|
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
k8s-ci-robot
added
the
cncf-cla: yes
Address #931