The registry reef

Every command that runs an image registry in the cluster and publishes to it

O reef registry

Todos os comandos que rodam um registry de imagens no cluster e publicam nele

Opening · the kinds

A Registry runs where images live, a Repository holds who may push

  • Registry, the default kind: spec has owner, mandate and purge (#1235); status has nereid, pullAddress, internalAddress and namespace
  • Repository: spec has registry and owner; status has image and pushIdentity, a ServiceAccount whose tokens expire (#1010)
  • One writer per field: the person writes spec, the Nereid writes status
Abertura · os kinds

Um Registry roda onde as imagens ficam, um Repository diz quem pode publicar

  • Registry, o kind padrão: o spec tem owner, mandate e purge (#1235); o status tem nereid, pullAddress, internalAddress e namespace
  • Repository: o spec tem registry e owner; o status tem image e pushIdentity, uma ServiceAccount cujos tokens expiram (#1010)
  • Um escritor por campo: a pessoa escreve o spec, o Nereid escreve o status
Registry · registry createbuilt #1011

create asks for a registry, and names who makes it

Registry · registry createpronto #1011

O create pede um registry e diz quem o faz

~/example
# A registry, through the reef's default Mandate$ nereus registry create mainsecrets/vaults/registries createdregistry/registries/main created (mandate: zot, nereid: zot) Next steps:   nereus registry get main # What it would write, as apply takes it, changing nothing$ nereus registry create main \    --owner project/shop \    --dry-run \    --output yamlapiVersion: registry.getnereus.dev/v1alpha1kind: Registrymetadata:  name: mainspec:  owner:    kind: Project    name: shop
Registry · create refusesbuilt #1011

create fails when it exists, and lists what to run

Registry · create recusapronto #1011

O create falha quando já existe e lista o que rodar

~/example
# The same name twice$ nereus registry create main✗ registry/registries/main already exists. To change it, run:  # write it as a file, then apply the file  nereus registry create main --dry-run --output yaml > main.yaml  nereus registry apply --from-file main.yaml
Registry · registry getbuilt #1011

get gives the address an image reference uses

Registry · registry getpronto #1011

O get dá o endereço que uma referência de imagem usa

~/example
# Who runs it, the address to pull from, and whether it is ready$ nereus registry get mainNAME  NEREID  PURGE  PULL-ADDRESS     READYmain  zot     168h   localhost:31874  True credential: secret registries/main-pull (vault registries) localhost:31874 is a NodePort, for an image reference on this cluster's nodes. Reading it takes the credential above. Next steps:   nereus registry repository publish hello --registry main --image hello:v1
Registry · registry listbuilt #1011

list shows every registry, one line each

Registry · registry listpronto #1011

O list mostra todos os registries, uma linha cada

~/example
# Every registry, in alphabetical order$ nereus registry listNAME  NEREID  PURGE  PULL-ADDRESS     READYmain  zot     168h   localhost:31874  True Next steps:   nereus registry get main
Registry · registry applybuilt #1011

apply takes files, and waits for the Nereid

Registry · registry applypronto #1011

O apply aceita arquivos e espera o Nereid

~/example
# Create or update from a file or a folder, and return at once$ nereus registry apply \    --from-file main.yaml \    --wait falseregistry/registries/main created Next steps:   nereus registry list
Registry · registry deletebuilt #1011

delete removes the registry and what its Nereid made

Registry · registry deletepronto #1011

O delete remove o registry e o que o Nereid dele fez

~/example
# Delete it, and wait until it is gone$ nereus registry delete mainregistry/registries/main deleted Next steps:   nereus registry list
Registry · registry purgebuilt #1235

A registry purges, when set, the images no Delivery runs

Registry · registry purgepronto #1235

Um registry apaga, quando configurado, as imagens que nenhuma Delivery roda

~/example
# A registry that deletes the images no Delivery runs, a week after they were built$ nereus registry create main \    --purge-unused 168hregistry/registries/main created (mandate: zot, nereid: zot; purge: images no Delivery runs, after 168h) Next steps:   nereus registry get main # What its Nereid would delete, what it keeps and why, changing nothing$ nereus registry purge main \    --dry-runWould delete 1 image no Delivery runs and older than 168h:  hello@sha256:6f1a2c9d0b3e...   created 2026-10-01T10:00:00ZKept 2 images: hello@sha256:9c4e7b1a5d2f... (Delivery hello-dev; the newest of its Repository), hello@sha256:2b8d4f6e1c3a... (Delivery hello-dev, previous)Checked by its Nereid at 2026-11-08T10:00:00Z.Nothing changed (--dry-run). Next steps:   nereus registry purge main
Publish · repository publishbuilt #1013

publish pushes an image with the platform's credential

Publicar · repository publishpronto #1013

O publish envia uma imagem com a credencial da plataforma

~/example
# The first tag of a repository$ nereus registry repository publish hello \    --registry main \    --image hello:v1registry/registries/main/repositories/hello createdregistry/registries/main/repositories/hello/tags/v1 published (sha256:ab12…) Next steps:   kubectl run hello --image localhost:31874/hello:v1 # A tag is never overwritten$ nereus registry repository publish hello \    --registry main \    --image hello:v1✗ registry/registries/main/repositories/hello/tags/v1 already exists, and a push token cannot overwrite a tag. To publish, run:  # the same image under a new tag  nereus registry repository publish hello --registry main --image hello:v2
References · references

Where the ideas came from

Referências · referências

De onde vieram as ideias