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
The source of truth for the commands of the release reef (#477). Every command here is built: the CLI builds them itself (cli/src/nereus/commands/release.py, #445 (the release reef)), and the outputs are what they print, recorded on a throwaway cluster by make scene-release, make scene-ingress (#745, Istio through the release reef) and the commands of #479.
The reef takes a chart from where it comes from to where it runs, without tying Nereus to Flux, Argo CD or plain Helm: the Mandate picks the Nereid (ADR 0010, reefs at runtime).
A fonte da verdade dos comandos do reef release (#477). Todo comando aqui está pronto: o próprio CLI os constrói (cli/src/nereus/commands/release.py, #445 (o reef release)), e as saídas são o que eles imprimem, gravadas num cluster descartável pelo make scene-release, pelo make scene-ingress (#745, o Istio pelo reef release) e pelos comandos do #479.
O reef leva um chart de onde ele vem até onde ele roda, sem amarrar o Nereus ao Flux, ao Argo CD ou ao Helm puro: o Mandate escolhe a Nereid (ADR 0010, reefs em runtime).
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
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
The four kinds live in release.getnereus.dev/v1alpha1, in the namespace Nereus runs in. Every kind takes create, apply, list, get and delete (ADR 0013, command conventions), and every change takes --dry-run.
A kind named after its reef takes the reef's own verbs: nereus release create is nereus release release create, and the slides of the Release use the short form.
Os quatro kinds vivem em release.getnereus.dev/v1alpha1, no namespace onde o Nereus roda. Todo kind aceita create, apply, list, get e delete (ADR 0013, convenções de comando), e toda mudança aceita --dry-run.
Um kind com o nome do seu reef usa os verbos do próprio reef: nereus release create é nereus release release create, e os slides da Release usam a forma curta.
What comes before the first chart?
O que vem antes do primeiro chart?
One command applies the release reef, with its four kinds
Um comando aplica o reef release, com os seus quatro kinds
# 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
The reef comes first, with no tool behind it. Its commands appear in the CLI as soon as it exists; until a Nereid looks after it, nothing writes the status of its objects.
O reef vem primeiro, sem ferramenta por trás. Os seus comandos aparecem no CLI assim que ele existe; até uma Nereid cuidar dele, nada escreve o status dos seus objetos.
The reference-release Nereid answers every kind with no tool, through the reference Mandate
A Nereid reference-release responde a todo kind sem ferramenta, pelo Mandate reference
# 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>
The reference Nereid is the reef's reference (controllers/reference/reefs/release.py): it answers a Repository, a Source, a Target and a Release as a real Nereid would, so every command works end to end without Flux. #486 (the fake Nereid became the reference Nereid of every reef) named it so.
Its image is built and pushed by the scene (make reference builds it alone, to the local registry nereus init creates); the digest after pinned to changes with each build.
A Nereid de referência é a referência do reef (controllers/reference/reefs/release.py): ela responde a um Repository, um Source, um Target e uma Release como uma Nereid real, então todo comando funciona de ponta a ponta sem o Flux. O #486 (a Nereid fake virou a Nereid de referência de todos os reefs) lhe deu esse nome.
A sua imagem é construída e publicada pelo scene (make reference a constrói sozinha, no registry local que o nereus init cria); o digest depois de pinned to muda a cada build.
The flux Nereid installs Flux and becomes the default through its Mandate
A Nereid flux instala o Flux e vira a padrão pelo seu Mandate
# 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>
The flux Nereid runs no tool next to it: it installs Flux in the cluster first, as the openbao Nereid runs OpenBao. Only the two controllers the reef uses, source-controller and helm-controller, from Flux's install.yaml of the version the CLI pins, refused unless its digest is the pinned one. Applying it again changes nothing; who upgrades Flux is #449.
One Nereid per reef until #72: delete the reference one first (nereus nereid delete reference-release); its Mandate and the reef's objects stay. Switching to Argo CD later is another Nereid and another Mandate, with the same commands.
A Nereid flux não roda ferramenta ao lado: ela instala o Flux no cluster primeiro, como a Nereid openbao roda o OpenBao. Só os dois controllers que o reef usa, source-controller e helm-controller, do install.yaml do Flux na versão que o CLI fixa, recusado se o digest não for o fixado. Aplicá-la de novo não muda nada; quem atualiza o Flux é o #449.
Uma Nereid por reef até o #72: apague a de referência antes (nereus nereid delete reference-release); o seu Mandate e os objetos do reef ficam. Trocar para o Argo CD depois é outra Nereid e outro Mandate, com os mesmos comandos.
Where does the chart come from?
De onde vem o chart?
A repository says where the charts come from
Um repository diz de onde os charts vêm
# 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>
--type is http (a Helm repository), oci (an OCI registry) or git. A private registry takes --type oci and --secret <secret>, a secret of the secrets reef.
READY comes from the Nereid of the reef's default Mandate, which writes the status of every Repository, Source and Target (ADR 0005, Nereids publish endpoints and commands in status).
--type é http (um repositório Helm), oci (um registry OCI) ou git. Um registry privado leva --type oci e --secret <secret>, um secret do reef secrets.
O READY vem da Nereid do Mandate padrão do reef, que escreve o status de todo Repository, Source e Target (ADR 0005, as Nereids publicam endpoints e comandos no status).
Apply takes a file, and applying what already holds changes nothing
O apply recebe um arquivo, e aplicar o que já vale não muda nada
# 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
create builds from flags, apply takes files (ADR 0013): create --dry-run --output yaml writes the object as apply --from-file takes it, whether it exists or not. apply reports created when the repository is new, configured when the file changes it, unchanged when it already holds. A folder of files works too.
O create monta a partir de flags, o apply recebe arquivos (ADR 0013): create --dry-run --output yaml escreve o objeto como o apply --from-file o recebe, exista ele ou não. O apply reporta created quando o repository é novo, configured quando o arquivo o muda, unchanged quando ele já vale. Uma pasta de arquivos também serve.
The list shows every repository and whether it is ready
A lista mostra todo repository e se ele está pronto
# Every repository$ nereus release repository listNAME TYPE URL READYcodecentric http https://codecentric.github.io/helm-charts True
--output yaml prints the objects themselves. With no repository, the list says so and points to nereus release repository create --help.
--output yaml imprime os próprios objetos. Sem nenhum repository, a lista diz isso e aponta para nereus release repository create --help.
One repository, by its name
Um repository, pelo seu nome
# One repository$ nereus release repository get codecentricNAME TYPE URL READYcodecentric http https://codecentric.github.io/helm-charts True
get takes --watch, which prints a line each time the repository changes, and --output yaml.
O get aceita --watch, que imprime uma linha cada vez que o repository muda, e --output yaml.
A repository goes once no source names it
Um repository sai quando nenhum source o nomeia
# Delete the repository$ nereus release repository delete codecentric✓ release/repositories/codecentric deleted Next steps: nereus release repository list
delete is refused while another object names the one deleted, here a Source of the repository; the refusal names it and the command that deletes it first. --dry-run says what would be deleted.
O delete é recusado enquanto outro objeto nomeia o que é apagado, aqui um Source do repository; a recusa o nomeia, com o comando que o apaga antes. --dry-run diz o que seria apagado.
Which chart, at which version?
Qual chart, em qual versão?
A source is one chart of a repository, at one version
Um source é um chart de um repository, numa versão
# 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
create fails when the source exists, and prints how to change it: write it as a file, then apply the file (ADR 0013).
O create falha quando o source existe, e imprime como mudá-lo: escrever como arquivo, depois aplicar o arquivo (ADR 0013).
A new version is one file away
Uma versão nova fica a um arquivo de distância
# 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
Every Release of the source follows it: the Nereid of each Release's Mandate moves it to the new version. The slides of the Release show 7.0.2 for that reason. The file is the object: keep it in git, and the next change is an edit of the file and the same apply.
Toda Release do source o acompanha: a Nereid do Mandate de cada Release a leva para a versão nova. Os slides da Release mostram 7.0.2 por isso. O arquivo é o objeto: guarde-o no git, e a próxima mudança é editar o arquivo e o mesmo apply.
The list shows every source with its chart and version
A lista mostra todo source com o seu chart e a sua versão
# Every source$ nereus release source listNAME REPOSITORY CHART VERSION DIGEST READYkeycloak codecentric keycloakx 7.0.2 - True
--output yaml prints the objects themselves.
--output yaml imprime os próprios objetos.
One source, by its name
Um source, pelo seu nome
# One source$ nereus release source get keycloakNAME REPOSITORY CHART VERSION DIGEST READYkeycloak codecentric keycloakx 7.0.2 - True
get takes --watch and --output yaml.
O get aceita --watch e --output yaml.
Publishing goes through the platform, with its credential, never yours
Publicar passa pela plataforma, com a credencial dela, nunca a sua
# 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>
No token of the external registry ever sits on the person's machine (#1229, the ADR "An external registry's push credential is the Repository's secret"): the CLI packages the chart and uploads it to a registry of the cluster with a ten-minute push token, as nereus registry repository publish does an image; the flux Nereid copies it by digest with the Repository's --secret, delivered by a SecretBinding for the copy alone, and checks the digest the target answers. The registry reef is required. A GitHub App token replaces the personal one later (#1250).
Nenhum token do registry externo fica na máquina da pessoa (#1229, the ADR "An external registry's push credential is the Repository's secret"): o CLI empacota o chart e o envia a um registry do cluster com um push token de dez minutos, como nereus registry repository publish faz com uma imagem; a Nereid flux o copia por digest com o --secret do Repository, entregue por um SecretBinding só para a cópia, e confere o digest que o destino responde. O registry reef é obrigatório. Um token de GitHub App substitui o pessoal depois (#1250).
A source in use is refused, with what to delete first
Um source em uso é recusado, com o que apagar antes
# 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
Nothing is left pointing at what is gone: the refusal names the release and the command that deletes it ([nereus release delete](#release-delete)).
Nada fica apontando para o que saiu: a recusa nomeia a release e o comando que a apaga ([nereus release delete](#release-delete)).
Where does it go?
Para onde ele vai?
A target is a namespace, of an environment or of the cluster Nereus runs in
Um target é um namespace, de um ambiente ou do cluster onde o Nereus roda
# 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
--environment is optional: with none, the target is the cluster Nereus runs in. With one, the flux Nereid installs into that environment's cluster, and a target whose environment is missing or not Ready is not Ready and never falls back to the cluster Nereus runs in.
--environment é opcional: sem ele, o target é o cluster onde o Nereus roda. Com ele, a Nereid flux instala no cluster desse environment, e um target cujo environment não existe ou não está Ready não fica Ready e nunca cai no cluster onde o Nereus roda.
Applying the same target again changes nothing
Aplicar o mesmo target de novo não muda nada
# 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
A changed file reports configured, as [nereus release source apply](#source-apply) shows.
Um arquivo mudado reporta configured, como mostra o [nereus release source apply](#source-apply).
The list shows every target with its environment and namespace
A lista mostra todo target com o seu ambiente e o seu namespace
# Every target$ nereus release target listNAME ENVIRONMENT NAMESPACE READYdev-identity dev identity True
--output yaml prints the objects themselves.
--output yaml imprime os próprios objetos.
One target, by its name
Um target, pelo seu nome
# One target$ nereus release target get dev-identityNAME ENVIRONMENT NAMESPACE READYdev-identity dev identity True
get takes --watch and --output yaml.
O get aceita --watch e --output yaml.
A target goes once no release names it
Um target sai quando nenhuma release o nomeia
# Delete the target$ nereus release target delete dev-identity✓ release/targets/dev-identity deleted Next steps: nereus release target list
Like a source, a target in use is refused, with the release to delete first.
Como um source, um target em uso é recusado, com a release a apagar antes.
How does a chart start running?
Como um chart começa a rodar?
A release runs a source in a target, through the reef's default Mandate
Uma release roda um source num target, pelo Mandate padrão do reef
# 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
The release goes through the reef's default Mandate, or the one --mandate names, and the output names the Nereid that took it. Pending until the Nereid writes its status; with the reference Nereid, Ready at the source's version at once.
A release passa pelo Mandate padrão do reef, ou pelo que o --mandate nomeia, e a saída nomeia a Nereid que a assumiu. Pending até a Nereid escrever o seu status; com a Nereid de referência, Ready na versão do source na hora.
Values and a Mandate of your choice, with Flux installing the chart
Values e um Mandate à sua escolha, com o Flux instalando o chart
# 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
--values-file holds the chart's values; the scene's are replicas: 1, fullnameOverride: keycloak, Keycloak's dev mode and a local cache stack (test/scene-release). Recorded by make scene-release, where the source stays at 7.0.1.
Failed comes only once Flux stops retrying: the Nereid copies the HelmRelease's conditions into the Release's status, with phase and version.
O --values-file guarda os values do chart; os do scene são replicas: 1, fullnameOverride: keycloak, o modo dev do Keycloak e uma pilha de cache local (test/scene-release). Gravado pelo make scene-release, onde o source fica em 7.0.1.
Failed só vem quando o Flux para de tentar: a Nereid copia as conditions do HelmRelease para o status da Release, com phase e version.
A release asks for its secrets by name, and its values never pass through Nereus
Uma release pede os seus secrets pelo nome, e os valores nunca passam pelo Nereus
# 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
--secret <vault>/<secret> asks for a Kubernetes Secret in the Target's namespace, every key, for a chart that reads a Secret by name; --secret-value <path>=<vault>/<secret>/<key> puts one key into one field of the values, through a binding in nereus-system that the HelmRelease's valuesFrom reads (#533). A bare secret name means the vault default.
Into an Environment (#877), --secret-value binds in the Environment's namespace on the host, env-<nereid>-<environment>, which the vault must allow by name; --secret is refused there until #1065.
The CLI refuses before it writes anything when the secret does not exist, the key is not in it, or the vault does not allow the namespace; the Nereid writes the HelmRelease only once each binding is Ready, and BindingFailed says when one cannot be. Recorded by make scene-release.
--secret <vault>/<secret> pede um Secret do Kubernetes no namespace do Target, com todas as chaves, para um chart que lê um Secret pelo nome; --secret-value <path>=<vault>/<secret>/<key> coloca uma chave num campo dos values, por um binding em nereus-system que o valuesFrom do HelmRelease lê (#533). Um nome de secret sozinho quer dizer o vault default.
Num Environment (#877), o --secret-value faz o binding no namespace do Environment no host, env-<nereid>-<environment>, que o vault precisa permitir pelo nome; o --secret é recusado ali até o #1065.
A CLI recusa antes de escrever qualquer coisa quando o secret não existe, a chave não está nele ou o vault não permite o namespace; a Nereid escreve o HelmRelease só quando cada binding está Ready, e BindingFailed diz quando um não pode ficar.
One folder holds the whole release, and the second apply changes nothing
Uma pasta guarda a release inteira, e o segundo apply não muda nada
# 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
apply is what a script or a pipeline runs: the same folder every time, created the first time, unchanged after. nereus release apply takes every kind of the reef and writes Repositories, then Sources, Targets and Releases; nereus release source apply takes Sources only. A reference that does not exist yet is the Nereid's to report, in the status. It waits until the Nereid answered the new generation Ready and fails when it Failed or after --timeout; --wait=false returns once written.
O apply é o que um script ou um pipeline roda: a mesma pasta toda vez, created na primeira, unchanged depois. O nereus release apply recebe todo kind do reef e escreve Repositories, depois Sources, Targets e Releases; o nereus release source apply recebe só Sources. Uma referência que ainda não existe fica para a Nereid reportar, no status. Ele espera a Nereid responder Ready à nova geração e falha quando ela responde Failed ou depois do --timeout; --wait=false volta assim que escreve.
The list shows every release, its version and the Nereid behind it
A lista mostra toda release, a sua versão e a Nereid por trás
# Every release$ nereus release listNAME SOURCE TARGET VERSION NEREID STATUSkeycloak-reference keycloak dev-identity 7.0.2 reference-release Ready
STATUS is Pending, Progressing, Ready or Failed, written by the Nereid of the release's Mandate.
STATUS é Pending, Progressing, Ready ou Failed, escrito pela Nereid do Mandate da release.
One release, by its name
Uma release, pelo seu nome
# One release$ nereus release get keycloak-referenceNAME SOURCE TARGET VERSION NEREID STATUSkeycloak-reference keycloak dev-identity 7.0.2 reference-release Ready
--watch prints a line each time the release changes, until it is Ready or Failed ([nereus release create](#release-create) shows it).
O --watch imprime uma linha cada vez que a release muda, até ficar Ready ou Failed (o [nereus release create](#release-create) mostra isso).
Deleting a release uninstalls its chart
Apagar uma release desinstala o seu chart
# 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
With Flux, deleting the Release deletes the HelmRelease the Nereid wrote, and Flux uninstalls the chart. Then its source and its target can go.
delete waits until the Nereid removed what it made, as kubectl delete does: the Release keeps its cleanup finalizer meanwhile, and list and get show it Terminating. A Nereid that writes steps in its status gets a line per step as it changes (time, ✓ done, … in progress, · pending, ✗ failed, name, message); a failed cleanup ends with exit 1. --wait=false returns at once, --timeout bounds the wait.
Com o Flux, apagar a Release apaga o HelmRelease que a Nereid escreveu, e o Flux desinstala o chart. Depois o seu source e o seu target podem sair.
O delete espera até a Nereid remover o que fez, como o kubectl delete: a Release mantém o seu finalizer de cleanup enquanto isso, e list e get a mostram Terminating. Uma Nereid que escreve steps no seu status ganha uma linha por step quando ele muda (hora, ✓ feito, … em andamento, · pendente, ✗ falhou, nome, mensagem); um cleanup que falha termina com exit 1. --wait=false retorna na hora, --timeout limita a espera.
How does traffic reach the cluster?
Como o tráfego chega ao cluster?
The Gateway API CRDs come first, applied by hand for now
Os CRDs da Gateway API vêm primeiro, aplicados à mão por enquanto
# 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
The cluster's ingress is Istio's gateway, installed through the release reef (#727 (the cluster's ingress), #745 (Istio through the release reef)). Before istiod starts, the Gateway API CRDs (Custom Resource Definitions) must exist, so istiod serves its Gateway classes.
A stand-in: kubectl apply --server-side of the release's standard-install.yaml, until the release reef installs manifests from git (#751). Recorded by make scene-ingress, on a throwaway cluster.
O ingress do cluster é o gateway do Istio, instalado pelo reef release (#727 (o ingress do cluster), #745 (o Istio pelo reef release)). Antes do istiod subir, os CRDs (Custom Resource Definitions) da Gateway API precisam existir, para o istiod servir as suas Gateway classes.
Um stand-in: kubectl apply --server-side do standard-install.yaml da release, até o reef release instalar manifests do git (#751). Gravado pelo make scene-ingress, num cluster descartável.
Istio's charts come from its own Helm repository
Os charts do Istio vêm do seu próprio repositório Helm
# 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
READY is False until Flux fetched the repository's index: the flux Nereid copies the HelmRepository's condition into the Repository's status a few seconds later.
O READY fica False até o Flux buscar o índice do repositório: a Nereid flux copia a condition do HelmRepository para o status do Repository alguns segundos depois.
Three charts at one pinned version: base and istiod first
Três charts numa versão fixada: base e istiod primeiro
# 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>
Istio 1.30.4, the latest stable on 2026-10-31, pinned (#727): the three charts move together, one version for all.
Istio 1.30.4, o último estável em 2026-10-31, fixado (#727): os três charts andam juntos, uma versão para todos.
Three charts at one pinned version: then the gateway, into istio-system
Três charts numa versão fixada: depois o gateway, para o istio-system
# 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
The target names no environment: the charts go to the cluster Nereus runs in, into istio-system, which the flux Nereid's HelmRelease creates (install.createNamespace).
O target não nomeia ambiente: os charts vão para o cluster onde o Nereus roda, no istio-system, que o HelmRelease da Nereid flux cria (install.createNamespace).
Each chart starts once the previous one is Ready: base first
Cada chart começa quando o anterior está Ready: o base primeiro
# 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
The release reef has no dependsOn yet (--depends-on is #749): the order is the person's, each nereus release create after nereus release get <previous> --watch shows Ready, never a sleep (#727).
O reef release ainda não tem dependsOn (o --depends-on é o #749): a ordem é de quem digita, cada nereus release create depois que o nereus release get <anterior> --watch mostra Ready, nunca um sleep (#727).
Then istiod, the control plane
Depois o istiod, o control plane
# 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
istiod finds the Gateway API CRDs when it starts and makes the Gateway class istio, which the Gateway of the last slide uses.
O istiod encontra os CRDs da Gateway API quando sobe e cria a Gateway class istio, que o Gateway do último slide usa.
Last, the ingress gateway, with no values of its own
Por último, o ingress gateway, sem values próprios
# 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
The chart's defaults fit: its Service istio-gateway (the release's name) is a LoadBalancer on port 80, which k3s's ServiceLB serves on the node and the k3d load balancer reaches from the host port of nereus init --ingress-port (#743).
Os padrões do chart servem: o seu Service istio-gateway (o nome da release) é um LoadBalancer na porta 80, que o ServiceLB do k3s serve no nó e o load balancer do k3d alcança pela porta do host do nereus init --ingress-port (#743).
A Gateway opens Envoy's listener, and with no route it answers 404
Um Gateway abre o listener do Envoy, e sem rota ele responde 404
# 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
Envoy opens no listener until a Gateway asks for one: without it, curl gets an empty reply. gateway.yaml is a Gateway API Gateway ingress in istio-system, of the class istio, bound to the chart's Service through addresses (istio-gateway.istio-system.svc.cluster.local, Istio's manual deployment), with one HTTP listener on port 80; applied by hand, the same stand-in as the CRDs (#751).
The 404 proves the path: the k3d port, the gateway's Service and Envoy answering with no route; the routes are #728. The scene's port is a free one, shown here as the kept cluster's 8080.
O Envoy não abre listener até um Gateway pedir um: sem ele, o curl recebe uma resposta vazia. O gateway.yaml é um Gateway ingress da Gateway API no istio-system, da class istio, ligado ao Service do chart pelo addresses (istio-gateway.istio-system.svc.cluster.local, o deployment manual do Istio), com um listener HTTP na porta 80; aplicado à mão, o mesmo stand-in dos CRDs (#751).
O 404 prova o caminho: a porta do k3d, o Service do gateway e o Envoy respondendo sem rota; as rotas são o #728. A porta do scene é uma livre, mostrada aqui como a 8080 do cluster mantido.