atmos kubernetes render
See exactly what Kubernetes YAML Atmos will send before anything touches the
cluster. render resolves stack values, inline manifests, generated files,
and provider inputs into the final manifests you can inspect, save, or pass to
another tool.
Put manifest files, Kustomize paths, inline objects, variables, environment, and default output paths in the Kubernetes component stack configuration.
Usage
atmos kubernetes render <component> --stack <stack> [options]
render resolves the component stack configuration, runs generation when
enabled, loads inline manifests, renders provider inputs, and writes the final
Kubernetes YAML. It does not contact the Kubernetes API server.
Output
By default, render writes a multi-document YAML stream to stdout:
atmos kubernetes render argocd -s plat-ue2-dev
Write a single multi-document YAML file:
atmos kubernetes render argocd -s plat-ue2-dev \
--output rendered/argocd.yaml
Write one file per Kubernetes object:
atmos kubernetes render argocd -s plat-ue2-dev \
--output-dir rendered/argocd \
--split
Configure a default render output in the component:
components:
kubernetes:
argocd:
render:
output:
path: rendered/clusters/{{ .vars.cluster }}/argocd
split: true
When split: true, path is treated as an output directory. Otherwise,
path is treated as a single output file.
Render all Kubernetes components in dependency order:
atmos kubernetes render --all -s plat-ue2-dev
Render affected Kubernetes components:
atmos kubernetes render --affected --base origin/main
--output and --output-dir are only supported when rendering one component.
For --all or --affected, configure component-level render.output paths.
Flags
--stack,-s(required)- Atmos stack.
--output(optional)- Write rendered manifests to a single multi-document YAML file.
--output-dir(optional)Write rendered manifests to a directory. Without
--split, Atmos writesmanifest.yamlin that directory.--split(optional)- Write one YAML file per Kubernetes object. Requires
--output-dir. --all(optional)- Render all Kubernetes components in dependency order.
--affected(optional)- Render affected Kubernetes components and their dependencies.
--include-dependents(optional)- With
--affected, include dependent Kubernetes components.