Release a chart¶
Release a Helm chart into a namespace, with its values and its secrets, through the Nereid that its Mandate picks: Flux here, swappable for another tool.
Before you start¶
- A cluster from Prepare the cluster with
--profile internal-developer-platform: it brings the release reef with the Nereidfluxas its default, and the secrets reef. - A secret
google-oauthfrom Keep a secret, in a vault that allows the target's namespace. - A file
keycloak-values.yamlwith the chart's values.
Steps¶
1. Point at the chart repository¶
A Repository says where charts come from: http for a Helm repository, oci for a registry.
nereus release repository create codecentric \
--url https://codecentric.github.io/helm-charts \
--type http
✓ release/repositories/codecentric created
NAME TYPE URL READY
codecentric http https://codecentric.github.io/helm-charts True
Next steps:
nereus release source create <name> --repository codecentric --chart <chart> --version <version>
2. Pick the chart and its version¶
A Source is one chart at one version.
nereus release source create keycloak \
--repository codecentric \
--chart keycloakx \
--version 7.0.1
✓ release/sources/keycloak created
NAME REPOSITORY CHART VERSION DIGEST READY
keycloak codecentric keycloakx 7.0.1 - True
Next steps:
nereus release target create <name> --namespace <namespace>
3. Say where it goes¶
A Target is a namespace, made when missing. --environment picks an environment of the environment reef; without it, the target is in the cluster Nereus runs in.
nereus release target create dev-identity \
--environment dev \
--namespace identity
✓ release/targets/dev-identity created
NAME ENVIRONMENT NAMESPACE READY
dev-identity dev identity True
Next steps:
nereus release create <name> --source <source> --target dev-identity
4. Release it with its values and secrets¶
nereus release create puts the source in the target. --secret makes a Kubernetes Secret with every key of a secret in the target's namespace; --secret-value <path>=<secret>/<key> puts one key into one values field. The CLI refuses a vault that does not allow the namespace before writing anything.
nereus release create keycloak \
--source keycloak \
--target dev-identity \
--values-file keycloak-values.yaml \
--mandate flux \
--secret google-oauth \
--secret-value nereus.googleClientId=google-oauth/GOOGLE_CLIENT_ID
✓ release/releases/keycloak created (nereid: flux)
binding secrets/vaults/default/secrets/google-oauth/secretbindings/identity/keycloak
binding secrets/vaults/default/secrets/google-oauth/secretbindings/nereus-system/keycloak-values-google-oauth
Next steps:
nereus release get keycloak --watch
Check it worked¶
nereus release get --watch follows the release: the secret bindings first, then the chart, until it is Ready.
nereus release get keycloak \
--watch
NAME SOURCE TARGET VERSION NEREID STATUS
keycloak keycloak dev-identity 7.0.1 flux Pending
2026-10-30T07:53:21Z ✓ binding 2 Secrets ready: identity/keycloak, nereus-system/keycloak-values-google-oauth.
2026-10-30T07:53:21Z ✓ helmrelease Wrote the Flux HelmRelease keycloak.
keycloak keycloak dev-identity 7.0.1 flux Progressing
keycloak keycloak dev-identity 7.0.1 flux Ready
A release that fails shows Failed once Flux stops retrying; a refused namespace or a failed binding shows BindingFailed.
Next¶
- Run a registry to publish your own chart with
nereus release source publish. - Follow the golden path: your own image, deployed through a ready-made chart into an Environment of its own.
Learn more¶
- The release reef: repositories, sources, targets and releases, every command.
- Runtime and profiles: why the Mandate, not the reef, picks Flux.