|
| 1 | +# Frequently Asked Questions (FAQ) |
| 2 | + |
| 3 | +This answers common questions about the CNCF Kubernetes AI Conformance program. |
| 4 | + |
| 5 | +### What is CNCF Kubernetes AI Conformance? |
| 6 | + |
| 7 | +The CNCF Kubernetes AI Conformance defines a set of capabilities, APIs, and configurations that a Kubernetes cluster must offer to reliably run AI/ML workloads. A Kubernetes platform or distribution must be certified as Kubernetes conformant before it can be certified as AI conformant. |
| 8 | + |
| 9 | +### What are the goals of the AI Conformance program? |
| 10 | + |
| 11 | +The primary goals of the program are to: |
| 12 | +* Simplify AI/ML on Kubernetes and accelerate adoption. |
| 13 | +* Guarantee interoperability and portability for AI workloads. |
| 14 | +* Enable ecosystem growth for AI tools on an industry standard foundation. |
| 15 | + |
| 16 | +### Will there be AI conformance tests? |
| 17 | + |
| 18 | +Not until 2026. For KubeCon NA 2025, each platform vendor will self-certify by filling out a questionnaire. |
| 19 | + |
| 20 | +### Why are some requirements conditional? |
| 21 | + |
| 22 | +The context of the requirements doesn’t always apply to all platforms. For example, autoscalers are not always applicable to on-prem clusters. In such cases, platforms can still be AI conformant by answering “Not Applicable” to the status and providing a justification. |
| 23 | + |
| 24 | +### Does a "Not Applicable" (N/A) status mean platforms can skip requirements? |
| 25 | + |
| 26 | +No. The justification for an N/A status cannot be "we don’t support this feature," but rather an explanation of why the requirement's context doesn't apply to the platform's environment. |
| 27 | + |
| 28 | +### Is self-certification per product or per company? |
| 29 | + |
| 30 | +AI conformance is certified per product and per configuration. For example, a cloud deployment is a different configuration from an air-gapped one. |
| 31 | + |
| 32 | +### What use cases is this conformance for? |
| 33 | + |
| 34 | +This effort is intended to cover all popular AI/ML workloads, including but not limited to training, inference, and agentic workloads. It is important to note that while not every workload type will use every single conformant feature, they all benefit from running on a standardized and capable platform. This ensures a consistent and interoperable environment for the entire AI/ML lifecycle. |
| 35 | + |
| 36 | +### Why a unified AI conformance instead of separate ones for training and serving? |
| 37 | + |
| 38 | +A unified approach is taken to avoid fragmentation and ensure workload portability across platforms. This reflects the increasing convergence of training and serving workloads. |
| 39 | + |
| 40 | +### What is the expected revision cycle for conformance? |
| 41 | + |
| 42 | +The revision cycle will be aligned with the release cycles of Kubernetes. |
0 commit comments