The release reef

Every command of the release reef: where a chart comes from, what it is, where it goes and the release itself

O reef release

Todos os comandos do reef release: de onde um chart vem, o que ele é, para onde vai e o próprio release

Opening · kinds

Four kinds, each one answering one question

  • Repository: where the chart comes from, a Helm repository, an OCI registry or Git · nereus release repository
  • Source: what is released, a chart of a repository at a version · nereus release source
  • Target: where it goes, a namespace of an environment or of the cluster Nereus runs in · nereus release target
  • Release: a source running in a target, with its values · nereus release
Abertura · kinds

Quatro kinds, cada um respondendo uma pergunta

  • Repository: de onde o chart vem, um repositório Helm, um registry OCI ou o Git · nereus release repository
  • Source: o que é instalado, um chart de um repositório numa versão · nereus release source
  • Target: para onde ele vai, um namespace de um ambiente ou do cluster onde o Nereus roda · nereus release target
  • Release: um source rodando num target, com os seus values · nereus release
Setup

What comes before the first chart?

Preparação

O que vem antes do primeiro chart?

Setup · reefbuilt

One command applies the release reef, with its four kinds

Preparação · reefpronto

Um comando aplica o reef release, com os seus quatro kinds

~/example
# Apply the release reef$ nereus reef apply release✓ core/reefs/release 0.1.0 created (release.getnereus.dev/v1alpha1: releases, repositories, sources, targets) Next steps:   nereus release --help  nereus nereid apply <nereid> --reef release
Setup · reference Nereidbuilt

The reference-release Nereid answers every kind with no tool, through the reference Mandate

Preparação · Nereid de referênciapronto

A Nereid reference-release responde a todo kind sem ferramenta, pelo Mandate reference

~/example
# Apply the reference Nereid to the release reef$ nereus nereid apply reference-release \    --reef release \    --image localhost:5111/reference-release-controller:0.1.0✓ core/nereids/reference-release created, Ready, pinned to sha256:b3c32d74194e: see 'nereus release --help' Next steps:   nereus nereid list # Make it the reef's default$ nereus mandate create reference \    --reef release \    --nereid reference-release \    --default✓ core/mandates/reference created (reef: release, nereid: reference-release, default)  clusterrole/controller-reference-release configured (nereid reference-release writes the status of mandate reference) Next steps:   nereus release repository create <name> --url <url>
Setup · Fluxbuilt

The flux Nereid installs Flux and becomes the default through its Mandate

Preparação · Fluxpronto

A Nereid flux instala o Flux e vira a padrão pelo seu Mandate

~/example
# Apply the flux Nereid to the release reef$ nereus nereid apply flux \    --reef release✓ core/nereids/flux created, Ready, pinned to sha256:e8731e3fb833: see 'nereus release --help'  flux/v2.9.6 created (source-controller, helm-controller in namespace flux-system) Next steps:   nereus mandate create flux --reef release --nereid flux --default # Make it the reef's default$ nereus mandate create flux \    --reef release \    --nereid flux \    --default✓ core/mandates/flux created (reef: release, nereid: flux, default)  core/mandates/reference configured (reef: release, nereid: reference-release, no longer the default)  clusterrole/controller-flux configured (nereid flux writes the status of mandate flux) Next steps:   nereus release repository create <name> --url <url>
Repository

Where does the chart come from?

Repository

De onde vem o chart?

Repository · createbuilt

A repository says where the charts come from

Repository · createpronto

Um repository diz de onde os charts vêm

~/example
# A Helm repository over http$ nereus release repository create codecentric \    --url https://codecentric.github.io/helm-charts \    --type http✓ release/repositories/codecentric createdNAME         TYPE  URL                                        READYcodecentric  http  https://codecentric.github.io/helm-charts  True Next steps:   nereus release source create <name> --repository codecentric --chart <chart> --version <version>
Repository · applybuilt

Apply takes a file, and applying what already holds changes nothing

Repository · applypronto

O apply recebe um arquivo, e aplicar o que já vale não muda nada

~/example
# Write the repository as a file$ nereus release repository create codecentric \    --url https://codecentric.github.io/helm-charts \    --type http \    --dry-run \    --output yaml > codecentric.yaml # Apply the file$ nereus release repository apply \    --from-file codecentric.yamlrelease/repositories/codecentric unchanged Next steps:   nereus release repository list
Repository · listbuilt

The list shows every repository and whether it is ready

Repository · listpronto

A lista mostra todo repository e se ele está pronto

~/example
# Every repository$ nereus release repository listNAME         TYPE  URL                                        READYcodecentric  http  https://codecentric.github.io/helm-charts  True
Repository · getbuilt

One repository, by its name

Repository · getpronto

Um repository, pelo seu nome

~/example
# One repository$ nereus release repository get codecentricNAME         TYPE  URL                                        READYcodecentric  http  https://codecentric.github.io/helm-charts  True
Repository · deletebuilt

A repository goes once no source names it

Repository · deletepronto

Um repository sai quando nenhum source o nomeia

~/example
# Delete the repository$ nereus release repository delete codecentric✓ release/repositories/codecentric deleted Next steps:   nereus release repository list
Source

Which chart, at which version?

Source

Qual chart, em qual versão?

Source · createbuilt

A source is one chart of a repository, at one version

Source · createpronto

Um source é um chart de um repository, numa versão

~/example
# The keycloakx chart at 7.0.1$ nereus release source create keycloak \    --repository codecentric \    --chart keycloakx \    --version 7.0.1✓ release/sources/keycloak createdNAME      REPOSITORY   CHART      VERSION  DIGEST  READYkeycloak  codecentric  keycloakx  7.0.1    -       True Next steps:   nereus release target create <name> --namespace <namespace> # Create it again$ nereus release source create keycloak \    --repository codecentric \    --chart keycloakx \    --version 7.0.1✗ release/sources/keycloak already exists. To change it, write it as a file, then apply the file:  nereus release source create keycloak --repository codecentric --chart keycloakx --version 7.0.1 --dry-run --output yaml > keycloak.yaml  nereus release source apply --from-file keycloak.yaml
Source · applybuilt

A new version is one file away

Source · applypronto

Uma versão nova fica a um arquivo de distância

~/example
# Write the source at 7.0.2 as a file$ nereus release source create keycloak \    --repository codecentric \    --chart keycloakx \    --version 7.0.2 \    --dry-run \    --output yaml > keycloak.yaml # Apply the file$ nereus release source apply \    --from-file keycloak.yaml✓ release/sources/keycloak configured Next steps:   nereus release source list
Source · listbuilt

The list shows every source with its chart and version

Source · listpronto

A lista mostra todo source com o seu chart e a sua versão

~/example
# Every source$ nereus release source listNAME      REPOSITORY   CHART      VERSION  DIGEST  READYkeycloak  codecentric  keycloakx  7.0.2    -       True
Source · getbuilt

One source, by its name

Source · getpronto

Um source, pelo seu nome

~/example
# One source$ nereus release source get keycloakNAME      REPOSITORY   CHART      VERSION  DIGEST  READYkeycloak  codecentric  keycloakx  7.0.2    -       True
Source · publishbuilt

Publishing goes through the platform, with its credential, never yours

Source · publishpronto

Publicar passa pela plataforma, com a credencial dela, nunca a sua

~/example
# An OCI repository whose push credential is a secret of the platform$ nereus release repository create ghcr \    --type oci \    --url oci://ghcr.io/getnereus/charts \    --secret ghcr-push✓ release/repositories/ghcr createdNAME  TYPE  URL                              READYghcr  oci   oci://ghcr.io/getnereus/charts   True Next steps:   nereus release source create <name> --repository ghcr --chart <chart> --version <version> # Package the chart, upload it to the cluster's registry, let the Nereid copy it$ nereus release source publish nereus \    --path charts/nereus \    --repository ghcrchart nereus 0.4.0 packagedregistry/registries/main/repositories/chart-nereus createduploaded to registry/registries/main/repositories/chart-nereus: sha256:ab12…✓ release/sources/nereus createdcopied to oci://ghcr.io/getnereus/charts/nereus@sha256:ab12…, readyNAME    REPOSITORY  CHART   VERSION  DIGEST                READYnereus  ghcr        nereus  0.4.0    sha256:ab12cd34ef56…  True Next steps:   nereus release create <name> --source nereus --target <target>
Source · deletebuilt

A source in use is refused, with what to delete first

Source · deletepronto

Um source em uso é recusado, com o que apagar antes

~/example
# A release still uses it$ nereus release source delete keycloak✗ source keycloak is used by release keycloak-reference.  Delete it first: nereus release delete keycloak-reference # Once the release is gone$ nereus release source delete keycloak✓ release/sources/keycloak deleted Next steps:   nereus release source list
Target

Where does it go?

Target

Para onde ele vai?

Target · createbuilt

A target is a namespace, of an environment or of the cluster Nereus runs in

Target · createpronto

Um target é um namespace, de um ambiente ou do cluster onde o Nereus roda

~/example
# The identity namespace of the dev environment$ nereus release target create dev-identity \    --environment dev \    --namespace identity✓ release/targets/dev-identity createdNAME          ENVIRONMENT  NAMESPACE  READYdev-identity  dev          identity   True Next steps:   nereus release create <name> --source <source> --target dev-identity
Target · applybuilt

Applying the same target again changes nothing

Target · applypronto

Aplicar o mesmo target de novo não muda nada

~/example
# Write the target as a file, then apply it$ nereus release target create dev-identity \    --environment dev \    --namespace identity \    --dry-run \    --output yaml > dev-identity.yaml # Apply the file$ nereus release target apply \    --from-file dev-identity.yamlrelease/targets/dev-identity unchanged Next steps:   nereus release target list
Target · listbuilt

The list shows every target with its environment and namespace

Target · listpronto

A lista mostra todo target com o seu ambiente e o seu namespace

~/example
# Every target$ nereus release target listNAME          ENVIRONMENT  NAMESPACE  READYdev-identity  dev          identity   True
Target · getbuilt

One target, by its name

Target · getpronto

Um target, pelo seu nome

~/example
# One target$ nereus release target get dev-identityNAME          ENVIRONMENT  NAMESPACE  READYdev-identity  dev          identity   True
Target · deletebuilt

A target goes once no release names it

Target · deletepronto

Um target sai quando nenhuma release o nomeia

~/example
# Delete the target$ nereus release target delete dev-identity✓ release/targets/dev-identity deleted Next steps:   nereus release target list
Release

How does a chart start running?

Release

Como um chart começa a rodar?

Release · createbuilt

A release runs a source in a target, through the reef's default Mandate

Release · createpronto

Uma release roda um source num target, pelo Mandate padrão do reef

~/example
# Run keycloak in dev-identity$ nereus release create keycloak-reference \    --source keycloak \    --target dev-identity✓ release/releases/keycloak-reference created (nereid: reference-release) Next steps:   nereus release get keycloak-reference --watch # Wait until it is ready$ nereus release get keycloak-reference \    --watchNAME                SOURCE    TARGET        VERSION  NEREID             STATUSkeycloak-reference  keycloak  dev-identity  -        -                  Pendingkeycloak-reference  keycloak  dev-identity  7.0.2    reference-release  Ready
Release · create with valuesbuilt

Values and a Mandate of your choice, with Flux installing the chart

Release · create com valuespronto

Values e um Mandate à sua escolha, com o Flux instalando o chart

~/example
# Keycloak with its values, through the flux Mandate$ nereus release create keycloak \    --source keycloak \    --target dev-identity \    --values-file keycloak-values.yaml \    --mandate flux✓ release/releases/keycloak created (nereid: flux) Next steps:   nereus release get keycloak --watch # Flux installs it$ nereus release get keycloak \    --watchNAME      SOURCE    TARGET        VERSION  NEREID             STATUSkeycloak  keycloak  dev-identity  7.0.1    flux    Pendingkeycloak  keycloak  dev-identity  7.0.1    flux    Progressingkeycloak  keycloak  dev-identity  7.0.1    flux    Ready
Release · create with secretsbuilt

A release asks for its secrets by name, and its values never pass through Nereus

Release · create com secretspronto

Uma release pede os seus secrets pelo nome, e os valores nunca passam pelo Nereus

~/example
# Keycloak with a Secret in its namespace and one key in its values$ 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 # The bindings first, then the HelmRelease$ nereus release get keycloak \    --watchNAME      SOURCE    TARGET        VERSION  NEREID             STATUSkeycloak  keycloak  dev-identity  7.0.1    flux    Pending2026-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    Progressingkeycloak  keycloak  dev-identity  7.0.1    flux    Ready
Release · applybuilt

One folder holds the whole release, and the second apply changes nothing

Release · applypronto

Uma pasta guarda a release inteira, e o segundo apply não muda nada

~/example
# Write the release as a file$ nereus release create keycloak-reference \    --source keycloak \    --target dev-identity \    --dry-run \    --output yaml > release/keycloak-reference.yaml # Apply the folder: every kind of the reef, in order$ nereus release apply \    --from-file release/✓ release/releases/keycloak-reference createdNAME                SOURCE    TARGET        VERSION  NEREID             STATUSkeycloak-reference  keycloak  dev-identity  -        reference-release  Pendingkeycloak-reference  keycloak  dev-identity  7.0.1    reference-release  Ready Next steps:   nereus release list # Apply it again$ nereus release apply \    --from-file release/release/releases/keycloak-reference unchangedNAME                SOURCE    TARGET        VERSION  NEREID             STATUSkeycloak-reference  keycloak  dev-identity  7.0.1    reference-release  Ready Next steps:   nereus release list
Release · listbuilt

The list shows every release, its version and the Nereid behind it

Release · listpronto

A lista mostra toda release, a sua versão e a Nereid por trás

~/example
# Every release$ nereus release listNAME                SOURCE    TARGET        VERSION  NEREID             STATUSkeycloak-reference  keycloak  dev-identity  7.0.2    reference-release  Ready
Release · getbuilt

One release, by its name

Release · getpronto

Uma release, pelo seu nome

~/example
# One release$ nereus release get keycloak-referenceNAME                SOURCE    TARGET        VERSION  NEREID             STATUSkeycloak-reference  keycloak  dev-identity  7.0.2    reference-release  Ready
Release · deletebuilt

Deleting a release uninstalls its chart

Release · deletepronto

Apagar uma release desinstala o seu chart

~/example
# See what would go$ nereus release delete keycloak-reference \    --dry-runrelease/releases/keycloak-reference would be deleted.Nothing changed (--dry-run). # Delete it$ nereus release delete keycloak-reference✓ release/releases/keycloak-reference deleted Next steps:   nereus release list
Ingress

How does traffic reach the cluster?

Ingress

Como o tráfego chega ao cluster?

Ingress · Gateway API

The Gateway API CRDs come first, applied by hand for now

Ingress · Gateway API

Os CRDs da Gateway API vêm primeiro, aplicados à mão por enquanto

~/example
# The Gateway API CRDs v1.7.0, standard channel$ kubectl apply \    --server-side \    --filename https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.7.0/standard-install.yamlcustomresourcedefinition.apiextensions.k8s.io/backendtlspolicies.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/gatewayclasses.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/gateways.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/grpcroutes.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/httproutes.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/listenersets.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/referencegrants.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/tcproutes.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/tlsroutes.gateway.networking.k8s.io serverside-appliedcustomresourcedefinition.apiextensions.k8s.io/udproutes.gateway.networking.k8s.io serverside-appliedvalidatingadmissionpolicy.admissionregistration.k8s.io/safe-upgrades.gateway.networking.k8s.io serverside-appliedvalidatingadmissionpolicybinding.admissionregistration.k8s.io/safe-upgrades.gateway.networking.k8s.io serverside-applied
Ingress · Istio's chartsbuilt

Istio's charts come from its own Helm repository

Ingress · charts do Istiopronto

Os charts do Istio vêm do seu próprio repositório Helm

~/example
# Istio's Helm repository$ nereus release repository create istio \    --url https://blob.istio.io/istio-release/charts \    --type http✓ release/repositories/istio createdNAME   TYPE  URL                                                  READYistio  http  https://blob.istio.io/istio-release/charts  False Next steps:   nereus release source create <name> --repository istio --chart <chart> --version <version> # Ready once Flux read its index$ nereus release repository get istioNAME   TYPE  URL                                                  READYistio  http  https://blob.istio.io/istio-release/charts  True
Ingress · sources · 1/2built

Three charts at one pinned version: base and istiod first

Ingress · sources · 1/2pronto

Três charts numa versão fixada: base e istiod primeiro

~/example
# The CRDs of Istio$ nereus release source create istio-base \    --repository istio \    --chart base \    --version 1.30.4✓ release/sources/istio-base createdNAME        REPOSITORY  CHART  VERSION  DIGEST  READYistio-base  istio       base   1.30.4   -       True Next steps:   nereus release target create <name> --namespace <namespace> # The control plane$ nereus release source create istiod \    --repository istio \    --chart istiod \    --version 1.30.4✓ release/sources/istiod createdNAME    REPOSITORY  CHART   VERSION  DIGEST  READYistiod  istio       istiod  1.30.4   -       True Next steps:   nereus release target create <name> --namespace <namespace>
Ingress · sources · 2/2built

Three charts at one pinned version: then the gateway, into istio-system

Ingress · sources · 2/2pronto

Três charts numa versão fixada: depois o gateway, para o istio-system

~/example
# The ingress gateway$ nereus release source create istio-gateway \    --repository istio \    --chart gateway \    --version 1.30.4✓ release/sources/istio-gateway createdNAME           REPOSITORY  CHART    VERSION  DIGEST  READYistio-gateway  istio       gateway  1.30.4   -       True Next steps:   nereus release target create <name> --namespace <namespace> # Where the three go$ nereus release target create istio-system \    --namespace istio-system✓ release/targets/istio-system createdNAME          ENVIRONMENT  NAMESPACE     READYistio-system  -            istio-system  True Next steps:   nereus release create <name> --source <source> --target istio-system
Ingress · istio-basebuilt

Each chart starts once the previous one is Ready: base first

Ingress · istio-basepronto

Cada chart começa quando o anterior está Ready: o base primeiro

~/example
# Istio's CRDs, through the flux Mandate$ nereus release create istio-base \    --source istio-base \    --target istio-system \    --mandate flux✓ release/releases/istio-base created (nereid: flux) Next steps:   nereus release get istio-base --watch # Wait until it is Ready$ nereus release get istio-base \    --watchNAME        SOURCE      TARGET        VERSION  NEREID             STATUSistio-base  istio-base  istio-system  -        -                  Pendingistio-base  istio-base  istio-system  1.30.4   flux    Pendingistio-base  istio-base  istio-system  1.30.4   flux    Progressingistio-base  istio-base  istio-system  1.30.4   flux    Ready
Ingress · istiodbuilt

Then istiod, the control plane

Ingress · istiodpronto

Depois o istiod, o control plane

~/example
# The control plane, once istio-base is Ready$ nereus release create istiod \    --source istiod \    --target istio-system \    --mandate flux✓ release/releases/istiod created (nereid: flux) Next steps:   nereus release get istiod --watch # Wait until it is Ready$ nereus release get istiod \    --watchNAME    SOURCE  TARGET        VERSION  NEREID             STATUSistiod  istiod  istio-system  -        -                  Pendingistiod  istiod  istio-system  1.30.4   flux    Pendingistiod  istiod  istio-system  1.30.4   flux    Progressingistiod  istiod  istio-system  1.30.4   flux    Ready
Ingress · istio-gatewaybuilt

Last, the ingress gateway, with no values of its own

Ingress · istio-gatewaypronto

Por último, o ingress gateway, sem values próprios

~/example
# The ingress gateway, once istiod is Ready$ nereus release create istio-gateway \    --source istio-gateway \    --target istio-system \    --mandate flux✓ release/releases/istio-gateway created (nereid: flux) Next steps:   nereus release get istio-gateway --watch # Wait until it is Ready$ nereus release get istio-gateway \    --watchNAME           SOURCE         TARGET        VERSION  NEREID             STATUSistio-gateway  istio-gateway  istio-system  -        -                  Pendingistio-gateway  istio-gateway  istio-system  1.30.4   flux    Pendingistio-gateway  istio-gateway  istio-system  1.30.4   flux    Progressingistio-gateway  istio-gateway  istio-system  1.30.4   flux    Ready
Ingress · curl

A Gateway opens Envoy's listener, and with no route it answers 404

Ingress · curl

Um Gateway abre o listener do Envoy, e sem rota ele responde 404

~/example
# The Gateway ingress: class istio, the gateway's Service, HTTP on port 80$ kubectl apply \    --filename gateway.yamlgateway.gateway.networking.k8s.io/ingress created # The host port, the gateway's Service, Envoy$ curl \    --include http://localhost:8080/HTTP/1.1 404 Not Founddate: Sat, 31 Oct 2026 20:51:28 GMTserver: istio-envoycontent-length: 0