Skip to main content

Kubernetes Configuration

Tell Atmos where Kubernetes component files live and which manifest workflow to use by default. These project-wide settings keep stack files focused on what to deploy while atmos.yaml defines how Kubernetes components are found and rendered.

Configuration​

atmos.yaml
components:
  kubernetes:
    # Base path to Kubernetes component directories
    base_path: components/kubernetes

    # Default manifest workflow for Kubernetes components
    provider: kubectl

    # Generate files from the component `generate` section before operations
    auto_generate_files: false

Configuration Reference​

base_path
Directory containing Kubernetes component directories. Relative paths are resolved from the Atmos base path. Defaults to components/kubernetes.
provider

Default provider when a stack component does not set provider. Supported values are kubectl and kustomize. Both providers use Go SDKs and do not require matching binaries. Defaults to kubectl.

auto_generate_files

When true, Atmos writes files from a component's generate block before rendering, diffing, applying, deploying, or deleting manifests. Defaults to false.

Providers​

The provider decides how Atmos turns component files into Kubernetes objects:

kubectl
Use this for plain YAML or JSON manifests. Atmos loads objects from paths and manifests, then resolves and applies them with Kubernetes clients.
kustomize
Use this when component paths point at Kustomize roots. Atmos renders the overlays before previewing, applying, or deleting objects.

The provider names describe behavior, not executable names. Atmos does not shell out to kubectl or kustomize for these component operations.