Policy on Feature Gates

[kannon92]

Hello,

I am very interested in the dynamic MIG and I see that it is under an alpha feature gate. This is fine but I was curious on graduation policy you have for feature gates?

What would be needed to bring your features gates to beta or stable?

[kannon92]

cc @jgehrcke @klueska

[shivamerla]

@kannon92 At the moment, we don’t have a formally documented process for promoting features in the DRA driver (e.g., Dynamic MIG).

Today, feature promotion is evaluated based on several factors like

• Feature completeness: The functionality is fully implemented and aligns with the intended design goals.
• Interoperability: The feature works reliably alongside other existing and upcoming features.
• Stability and soak time: The feature has been exercised in real-world or production-like environments for a sufficient period without major issues.

For now, any constraints or caveats are clearly documented in the release notes (see: https://github.com/NVIDIA/k8s-dra-driver-gpu/releases).

That said, we recognize that we need to establish clearer, documented promotion criteria and a more structured process for this. I will work on defining and documenting this with @a-mccarthy

[guptaNswati]

Thank you @kannon92 for bringing it up. We definitely need to define and document this process. @shivamerla let me take a stab at it. I have spent sometime on the KEPs. I will draft a proposal and submit for feedback.

I would refer these so that its aligned with upstream and post-donation:

• https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/0000-kep-process/README.md
• https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template