Skip to content

Gardener Achieves CNCF AI Conformance for Kubernetes

We are happy to announce that Gardener is one of the first Kubernetes offerings to report official AI Conformance, as defined by the Cloud Native Computing Foundation's (CNCF) Kubernetes AI Conformance Working Group. This significant milestone underscores Gardener's commitment to providing a robust, scalable, and reliable platform for running modern, resource-intensive AI and machine learning (ML) workloads.

What is Kubernetes AI Conformance?

As AI/ML applications become more prevalent, the need for a standardized environment to run them on Kubernetes has become critical. The CNCF's Kubernetes AI Conformance Working Group was established to address this need. It aims to define a clear, verifiable set of requirements that a Kubernetes distribution must meet to be considered "AI Conformant."

This conformance standard provides a trusted baseline for users, ensuring that a Kubernetes cluster is properly configured to handle the unique demands of AI workloads. It goes beyond basic Kubernetes conformance to verify specific capabilities related to hardware acceleration, drivers, and runtime environments, which are essential for the performance and stability of AI applications.

How Gardener Delivers AI Conformance

Achieving AI Conformance is based on the first requirements catalog published by the working group. Here’s how Gardener meets these stringent requirements:

Natively Integrated GPU Support

A cornerstone of our AI Conformance is the support of the NVIDIA GPU Operator for Garden Linux. Managing GPU drivers across a fleet of machines is notoriously complex, and the GPU Operator abstracts this complexity away from the user.

This ensures the correct NVIDIA drivers are installed and configured for your GPU nodes. Users no longer have to manually handle driver installations, version mismatches, or kernel module compilations. When you request a worker node with a GPU, the Operator ensures that it is ready for your AI workloads with the necessary drivers and CUDA libraries, making the powerful hardware directly accessible to your Kubernetes pods.

Meeting the Conformance Requirements

The AI Conformance standard specifies a catalog of requirements that a platform must satisfy. Gardener fulfills these by ensuring:

  • GPU Discovery and Allocation: Gardener-managed clusters correctly identify available GPUs on worker nodes and make them schedulable resources within Kubernetes. This allows users to simply request nvidia.com/gpu resources in their pod specifications.
  • Driver and Runtime Integrity: The conformance verifies that the correct NVIDIA drivers and container runtimes are in place to expose GPUs to containers. Gardener’s managed approach guarantees that these components are correctly installed and versioned.
  • Workload Execution: By passing the conformance tests, Gardener proves that it can reliably run sample AI/ML workloads that utilize GPU acceleration, confirming that the entire stack—from the operating system to the Kubernetes control plane—is functioning correctly.

What This Means for You

For developers and platform engineers running AI/ML applications, Gardener's AI Conformance provides tangible benefits:

  • Simplified Operations: Drastically reduces the operational burden of setting up and maintaining GPU-enabled Kubernetes clusters.
  • Increased Reliability: Provides a standardized, predictable environment, giving you the confidence to run production-grade AI workloads.
  • Faster Time-to-Value: Enables you to focus on developing your AI models and applications instead of wrestling with infrastructure configuration.

With Gardener, you can be assured that your Kubernetes clusters are not just capable but officially conformant for the next generation of AI-driven applications.

Further Reading

EU and German government funding logos

Funded by the European Union – NextGenerationEU.

The views and opinions expressed are solely those of the author(s) and do not necessarily reflect the views of the European Union or the European Commission. Neither the European Union nor the European Commission can be held responsible for them.