Skip to content

Kubernetes provider model

The Kubernetes provider model defines how Infrastructure as Code (IaC) tools manage and interact with Kubernetes clusters. It serves as the interface that allows infrastructure code to communicate with various Kubernetes environments, abstracting the underlying differences between distributions and hosting platforms.^[400-devops__08-Infrastructure-as-Code__pulumi.md]

Functionality

A provider package typically includes the necessary components to manage resources across different types of Kubernetes setups. This covers local development environments like Minikube, on-premises clusters, and cloud-hosted custom clusters^[400-devops__08-Infrastructure-as-Code__pulumi.md]. Additionally, the model supports managed services offered by major cloud providers, ensuring that resources within Google (GKE), Azure (AKS), and Amazon (EKS) can be provisioned and maintained consistently^[400-devops__08-Infrastructure-as-Code__pulumi.md].

Implementation

The practical application of this model often involves using general-purpose programming languages to define infrastructure rather than standard YAML configuration. This approach allows operators to define Kubernetes resources using familiar languages such as Java or JavaScript^[400-devops__08-Infrastructure-as-Code__pulumi.md]. The provider model facilitates this by handling the translation of code definitions into API calls that the Kubernetes cluster understands.

Sources

^[400-devops__08-Infrastructure-as-Code__pulumi.md]