Helm Configuration
Tell Atmos where native Helm component files live. These project-wide settings
keep stack files focused on what to deploy, while atmos.yaml defines how Helm
components are found. Charts are rendered and deployed through the Helm Go SDK,
so no helm or helmfile binary is required.
Configuration
Configuration Reference
base_path- Base directory for native Helm components. Local charts referenced with a relative
chartpath resolve under each component directory. Defaults tocomponents/helm. auto_generate_files- When
true, Atmos renders the componentgeneratesection into the component directory before Helm operations. Defaults tofalse. repositoriesReusable Helm chart repositories. Components can reference these with
chart: repo-name/chart-name. Component-levelrepositoriesentries override global entries with the samename.
Helm Repositories
Global repositories are declared once in atmos.yaml:
Supported repository fields:
name(required)- Repository name used in
repo/chartreferences. url(required)- HTTP chart repository URL.
username,password- Basic authentication credentials for the repository.
pass_credentials_all- Pass credentials to chart URLs on all domains, matching Helm's
--pass-credentialsbehavior. cert_file,key_file,ca_file- TLS client certificate, key, and CA bundle files.
insecure_skip_tls_verify- Skip TLS certificate verification for repository access.
Before template, diff, apply, or deploy, Atmos adds or updates these
repositories in Helm's local repository config and downloads their indexes into
Helm's repository cache. delete does not update repositories.
See the atmos helm command and the
Helm stack configuration for component-level fields.