The core of the CLI

The CLI's own commands: prepare a cluster, see how it is doing, and apply reefs, Nereids, Mandates and profiles

O core do CLI

Os comandos do próprio CLI: preparar um cluster, ver como ele está, e aplicar reefs, Nereids, Mandates e profiles

Opening · groups · 1/2

Eight groups, before any reef

  • init: prepares the cluster, core and a profile
  • status: one row per reef and its Nereid
  • doctor: one pass or fail per check
  • reef: a capability, its kinds and its command group
  • nereid: the controller that looks after a reef
  • mandate: binds a reef to a Nereid, with its params
Abertura · grupos · 1/2

Oito grupos, antes de qualquer reef

  • init: prepara o cluster, o core e um profile
  • status: uma linha por reef e a sua Nereid
  • doctor: um pass ou fail por verificação
  • reef: uma capacidade, os seus kinds e o seu grupo de comandos
  • nereid: o controller que cuida de um reef
  • mandate: liga um reef a uma Nereid, com os seus params
Opening · groups · 2/2

Eight groups, before any reef

  • profile: the reefs, Nereids and Mandates that come together
  • config: the SLO, the installation and your current owner
Abertura · grupos · 2/2

Oito grupos, antes de qualquer reef

  • profile: os reefs, Nereids e Mandates que vêm juntos
  • config: o SLO, a instalação e o seu owner atual
Init

How does a cluster become a Nereus instance?

Init

Como um cluster vira uma instância do Nereus?

Init · init --generate-filebuilt

The settings of init, written once to a file

Init · init --generate-filepronto

As configurações do init, escritas uma vez num arquivo

~/example
# Write the settings, and create nothing$ nereus init \    --create-cluster \    --name nereus-local \    --generate-fileSETTING            VALUE         SOURCEtarget             k3d           defaultcreate_cluster     true          flagname               nereus-local  flagingress_port       8080          defaultinstallation_name  nereus-local  cluster nameprofile            core          default✓ settings written to ~/.config/nereus/init.yaml: edit it, then run 'nereus init'
Init · init --dry-runbuilt

See each setting and where it came from

Init · init --dry-runpronto

Veja cada configuração e de onde ela veio

~/example
# What init will use, and nothing is created$ nereus init \    --dry-runSETTING            VALUE         SOURCEtarget             k3d           defaultcreate_cluster     true          ~/.config/nereus/init.yamlname               nereus-local  ~/.config/nereus/init.yamlingress_port       8080          ~/.config/nereus/init.yamlinstallation_name  nereus-local  ~/.config/nereus/init.yamlprofile            core          ~/.config/nereus/init.yaml
Init · initbuilt

Core in two Helm releases, each step with its time

Init · initpronto

O core em duas releases do Helm, cada passo com o seu tempo

~/example
# Install or upgrade core, from the settings file$ nereus init \    --yesSETTING            VALUE         SOURCEtarget             k3d           defaultcreate_cluster     true          ~/.config/nereus/init.yamlname               nereus-local  ~/.config/nereus/init.yamlingress_port       8080          ~/.config/nereus/init.yamlinstallation_name  nereus-local  ~/.config/nereus/init.yamlprofile            core          ~/.config/nereus/init.yaml✓ prerequisites             0.0s  docker 29.9.1, k3d 5.9.0, helm 4.1.4✓ registry localhost:5111   0.0s  reused✓ cluster nereus-local      0.1s  reused✓ kinds                     0.4s  release nereus-reefs revision 2✓ nereus                    1.1s  release nereus revision 2, profile core✓ installation              0.3s  kept nereus-local  total                     1.8s  slo 4m, 0% green✓ cluster ready in context k3d-nereus-local · config in ~/.config/nereus/config.yaml · values in ~/.config/nereus/values.yaml
Init · init --profilebuilt

A profile after core, installed in the cluster by thetis

Init · init --profilepronto

Um profile depois do core, instalado no cluster pelo thetis

~/example
# Core, then the profile internal-developer-platform$ nereus init \    --profile internal-developer-platform \    --yesSETTING            VALUE                        SOURCEtarget             k3d                          defaultcreate_cluster     true                         ~/.config/nereus/init.yamlname               nereus-local                 ~/.config/nereus/init.yamlingress_port       8080                         ~/.config/nereus/init.yamlinstallation_name  nereus-local                 ~/.config/nereus/init.yamlprofile            internal-developer-platform  flag✓ prerequisites             0.1s  docker 29.9.3, k3d 5.9.0, helm 4.1.4✓ registry localhost:5111   0.0s  reused✓ cluster nereus-local     16.8s  created✓ kinds                     0.4s  release nereus-reefs revision 1✓ nereus                    1.5s  release nereus revision 1, profile internal-developer-platform✓ installation              0.2s  created nereus-local✓ ready                    8m21s  12 Nereids ready, slowest keycloak 2m31s  slo 108% red✓ public key                0.0s  rsa-4096, SHA256:EyQwfBvDGJkXxcWzg6k5YtiwqRPAHcsv4cvNcH3B0QM, version 1  total                    8m40s  slo 8m, 108% red✓ cluster ready in context k3d-nereus-local · config in ~/.config/nereus/config.yaml · values in ~/.config/nereus/values.yaml Next steps:   nereus status ! init took 8m40s, over its time objective of 8m, within the 20% tolerance (9m36s); slowest steps: ready keycloak 2m31s, ready nereus-portal 2m15s, ready openbao 1m11s; shorten them, or raise the objective: nereus config slo set --local 9m
Init · init --targetbuilt

An undercloud on k3d, and the plan for the cloud

Init · init --targetpronto

Um undercloud no k3d, e o plano para a nuvem

~/example
# The settings file names the cloud azure and the installation tailwind$ nereus init \    --dry-run \    --yes✓ undercloud tailwind-undercloud on k3d    0s✓ installation tailwind, new               0s✓ Reef cloud, Nereid azure    0s Plan for Azure · northeurope · 9 requests · not run (--dry-run)  1  create   resource group        tailwind-platform  2  create   storage account       issuers0b7e4c1a93d24f6e  3  create   container             oidc  4  access   Storage Blob Data Contributor on issuers0b7e4c1a93d24f6e to you  5  publish  issuer documents (3)  6  create   managed identity      tailwind-cloud-provisioner  7  create   federated credential  tailwind-undercloud-azure  tagged with the installation and who asked  --show-requests for the why, URLs and tags Nothing ran in Azure. To run it:$ nereus init --yes --approve-access
Init · init --approve-accessbuilt

The plan approved, each line with its time

Init · init --approve-accesspronto

O plano aprovado, cada linha com o seu tempo

~/example
# Approve the whole run, undercloud included$ nereus init \    --approve-access✓ undercloud tailwind-undercloud on k3d    0s✓ installation tailwind, new               0s✓ Reef cloud, Nereid azure    0s Plan for Azure · northeurope · 9 requests · approved (--approve-access)  log: ~/.local/state/nereus/logs/20261019T221500Z-init.log✓ 1  create   resource group        tailwind-platform                             0s✓ 2  create   storage account       issuers0b7e4c1a93d24f6e                       0s✓ 3  create   container             oidc                                          0s✓ 4  access   Storage Blob Data Contributor on issuers0b7e4c1a93d24f6e to you     0s✓ 5  publish  issuer documents (3)                                                0s✓ 6  create   managed identity      tailwind-cloud-provisioner                    0s✓ 7  create   federated credential  tailwind-undercloud-azure                     0s  tagged with the installation and who asked  --show-requests for the why, URLs and tags ✓ azure exchanged its token as tailwind-cloud-provisioner Next, a reef that uses the cloud:$ nereus reef apply secrets --from-file ./reefs/secrets/
Status

How is each reef doing?

Status

Como está cada reef?

Status · statusbuilt

One row per reef and Nereid, core first

Status · statuspronto

Uma linha por reef e Nereid, o core primeiro

~/example
# How each reef is doing, through the Nereus API$ nereus statusREEF            NEREID    VERSION  STATUS         AGEauthentication  keycloak  0.1.0    Ready          2mcore            built-in  0.1.0    Ready          4mrelease         flux      0.1.0    Ready          3msecrets         openbao   0.1.0    Ready          4mtenancy         -         -        Ready          4m Registry  localhost:5111
Doctor

Is this instance healthy?

Doctor

Esta instância está saudável?

Doctor · doctorbuilt

One pass or fail per check, with the command that helps

Doctor · doctorpronto

Um pass ou fail por verificação, com o comando que ajuda

~/example
# Ten checks; one that did not run says so$ nereus doctorCHECK       RESULT   DETAILapi         fail     no Nereus instance: the CLI does not know its addresscapacity    skipped  needs apiworkloads   skipped  needs apinereids     skipped  needs apistore       skipped  needs apisecrets     skipped  needs apiissuer      skipped  needs apiregistry    skipped  needs apicli         pass     nereus and nrs on PATHcompletion  pass     nereus and nrs in ~/.bash_completions ✗ 1 of 10 checks failed, 7 skipped Next steps:   nereus login https://<the instance's address>
Doctor · versionbuilt

The version of this nereus, as --version prints it

Doctor · versionpronto

A versão deste nereus, como o --version a imprime

~/example
# The same line as nereus --version$ nereus versionnereus 0.1.31 # As data, for scripts and agents$ nereus version \    --output json{  "name": "nereus",  "version": "0.1.31"}
Reef

How does a capability arrive?

Reef

Como uma capacidade chega?

Reef · reef applybuilt

A reef applied from the version this CLI pins

Reef · reef applypronto

Um reef aplicado da versão que este CLI fixa

~/example
# Apply the reef release, with its kinds$ 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 # Again: no resourceVersion moved$ nereus reef apply releasecore/reefs/release unchanged
Reef · reef apply --from-filebuilt

A reef from local YAML, previewed first

Reef · reef apply --from-filepronto

Um reef de YAML local, visto antes

~/example
# What would change, and nothing changes$ nereus reef apply cloud \    --dry-runKIND                      NAME                        CHANGECustomResourceDefinition  clouds.cloud.getnereus.dev  createReef                      cloud                       createNothing changed (--dry-run). # From a folder of YAML$ nereus reef apply cloud \    --from-file ./cloud/✓ core/reefs/cloud 0.1.0 configured (cloud.getnereus.dev/v1alpha1: clouds)
Reef · reef createbuilt

create fails on a reef that exists, and says what changes it

Reef · reef createpronto

O create falha num reef que existe, e diz o que o muda

~/example
# As kubectl create does$ nereus reef create release✗ reef release already exists. To change it, run one of:  nereus reef apply release                     # the version this CLI pins  nereus reef apply release --image <ref>       # an OCI package  nereus reef apply release --from-file <file or folder>
Reef · reef listbuilt

Each reef with the Nereids that look after it

Reef · reef listpronto

Cada reef com as Nereids que cuidam dele

~/example
# Every reef$ nereus reef listREEF     NEREIDSrelease  -secrets  openbao
Reef · reef getbuilt

One reef in full: its group, kinds, Nereids and Mandates

Reef · reef getpronto

Um reef por inteiro: grupo, kinds, Nereids e Mandates

~/example
# The reef release, with its reference Nereid$ nereus reef get releaseName:      releaseGroup:     release.getnereus.dev/v1alpha1Version:   0.1.0Kinds:     Release, Repository, Source, TargetNereids:   reference-releaseMandates:  reference (default)Age:       2m
Reef · reef deletebuilt

With no Nereid left, the reef and its group go

Reef · reef deletepronto

Sem Nereid restante, o reef e o seu grupo vão embora

~/example
# Delete the reef; its kinds stay$ nereus reef delete release✓ core/reefs/release deleted
Nereid

Who looks after a reef?

Nereid

Quem cuida de um reef?

Nereid · nereid applybuilt

A Nereid from its image, pinned to the digest

Nereid · nereid applypronto

Uma Nereid da sua imagem, fixada pelo digest

~/example
# Apply the reference Nereid to the reef release$ 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:ffb8e8957c6e: see 'nereus release --help' Next steps:   nereus nereid list
Nereid · nereid apply --imagebuilt

Another image updates it in place, with no delete

Nereid · nereid apply --imagepronto

Outra imagem a atualiza no lugar, sem delete

~/example
# What would change$ nereus nereid apply reference-release \    --image localhost:5111/reference-release-controller:0.1.1 \    --dry-runWould configure core/nereids/reference-release for reef release: image sha256:ffb8e8957c6e → sha256:3f2a9c1d7e4b.Nothing changed (--dry-run). # The new image$ nereus nereid apply reference-release \    --image localhost:5111/reference-release-controller:0.1.1✓ core/nereids/reference-release configured, Ready, pinned to sha256:3f2a9c1d7e4b (was sha256:ffb8e8957c6e): see 'nereus release --help'
Nereid · nereid apply --publishbuilt #1951

Only the endpoints a person grants are ever published

Nereid · nereid apply --publishpronto #1951

Só os endpoints que uma pessoa concede são publicados

~/example
# Let the edge reef publish Triton's mcp endpoint$ nereus nereid apply triton \    --publish mcp✓ core/nereids/triton unchanged, Ready✓ core/nereids/triton configured (publishes: mcp) # Take the grant away$ nereus nereid apply triton \    --publish ""✓ core/nereids/triton unchanged, Ready✓ core/nereids/triton configured (publishes nothing)
Nereid · nereid createbuilt

create is apply that fails when the Nereid exists

Nereid · nereid createpronto

O create é o apply que falha quando a Nereid existe

~/example
# A new Nereid, from flags$ nereus nereid create reference-release \    --reef release \    --image localhost:5111/reference-release-controller:0.1.0✓ core/nereids/reference-release created, Ready, pinned to sha256:ffb8e8957c6e: see 'nereus release --help' Next steps:   nereus nereid list # Again: it exists, and the line names apply$ nereus nereid create reference-release \    --reef release✗ nereid reference-release already exists (reef: release). To change it, run:  nereus nereid apply reference-release --reef release
Nereid · nereid listbuilt

Each Nereid with its reefs, image and status

Nereid · nereid listpronto

Cada Nereid com os seus reefs, imagem e status

~/example
# Every Nereid$ nereus nereid listNEREID             REEFS    IMAGE                                                 STATUS  AGEreference-release  release  localhost:5111/reference-release-controller:0.1.0     Ready   10sopenbao            secrets  localhost:5111/openbao-controller:0.1.0               Ready   1m
Nereid · nereid getbuilt

One Nereid in full, with its Mandates

Nereid · nereid getpronto

Uma Nereid por inteiro, com os seus Mandates

~/example
# The keycloak Nereid$ nereus nereid get keycloakName:         keycloakReefs:        authenticationImage:        localhost:5111/keycloak-controller:0.1.0Digest:       sha256:0f4675ab231b4e6d4a439d0c7d8e5b07011f35802b38592851542cf56666be93Title:        authentication-keycloak-controllerDescription:  The keycloak Nereid of Nereus, for the authentication reefStatus:       ReadyMandates:     keycloak (default)Age:          2m
Nereid · nereid deletebuilt

Its commands and everything it ran go with it

Nereid · nereid deletepronto

Os seus comandos e tudo o que ela rodava vão junto

~/example
# The last Nereid of a reef another Nereid requires$ nereus nereid delete reference-release✗ reference-release is the last Nereid of reef release, which added Nereids require: reference-docs.  Remove them first, or go ahead with: nereus nereid delete reference-release --force # With nothing requiring it$ nereus nereid delete reference-release✓ core/nereids/reference-release deleted
Mandate

Which Nereid answers, and with which settings?

Mandate

Qual Nereid responde, e com quais configurações?

Mandate · mandate createbuilt #1273

A GitHub App is a Mandate of the github Nereid

Mandate · mandate createpronto #1273

Um GitHub App é um Mandate do Nereid github

~/example
# The App's identity, bound to the reef$ nereus mandate create github \    --reef authentication \    --nereid github \    --param appId=123456 \    --param privateKey=github-app-key \    --param allow=nereus-system:*:contents=read \    --param allow=example:example/app:metadata=read \    --default✓ core/mandates/github created (reef: authentication, nereid: github, default)  clusterrole/controller-github configured (nereid github writes the status of mandate github) Next steps:   nereus mandate list
Mandate · mandate applybuilt

apply creates or changes a Mandate's params

Mandate · mandate applypronto

O apply cria ou muda os params de um Mandate

~/example
# The portal's public address, in its Mandate$ nereus mandate apply nereus-portal \    --reef portal \    --nereid nereus-portal \    --param publicUrl=https://portal.example.com✓ core/mandates/nereus-portal configured (reef: portal, nereid: nereus-portal, default) Next steps:   nereus mandate list
Mandate · mandate listbuilt

A second Mandate of a reef, then the list

Mandate · mandate listpronto

Um segundo Mandate de um reef, depois a lista

~/example
# Another Mandate of the same reef and Nereid$ nereus mandate create corporate \    --reef authentication \    --nereid keycloak✓ core/mandates/corporate created (reef: authentication, nereid: keycloak)  clusterrole/controller-keycloak configured (nereid keycloak writes the status of mandate corporate) Next steps:   nereus mandate list # Every Mandate$ nereus mandate listMANDATE    REEF            NEREID    DEFAULT  STATUS  AGEcorporate  authentication  keycloak  false    Ready   3sdefault    secrets         openbao   true     Ready   1mkeycloak   authentication  keycloak  true     Ready   11s
Mandate · mandate getbuilt #1273

The Mandate's status says what the App may do

Mandate · mandate getpronto #1273

O status do Mandate diz o que o App pode fazer

~/example
# What the Nereid wrote, in the Mandate's status$ nereus mandate get githubName:           githubReef:           authenticationNereid:         githubDefault:        trueParams:         allow=nereus-system:*:contents=read;example:example/app:metadata=read, appId=123456, privateKey=github-app-keyStatus:         ReadyApp:            example-nereusInstallations:  example (all repositories)Permissions:    contents=read, metadata=readAge:            10sAllowed:  NAMESPACE      REPOSITORY   PERMISSIONS  nereus-system  *            contents=read  example        example/app  metadata=read
Mandate · mandate deletebuilt

The reef and the Nereid stay; its grant goes first

Mandate · mandate deletepronto

O reef e a Nereid ficam; a sua permissão sai antes

~/example
# Delete the second Mandate$ nereus mandate delete corporate✓ core/mandates/corporate deleted (reef: authentication, nereid: keycloak)  clusterrole/controller-keycloak configured (nereid keycloak no longer writes the status of mandate corporate) Next steps:   nereus mandate list
Profile

Which reefs and Nereids come together?

Profile

Quais reefs e Nereids vêm juntos?

Profile · profile listbuilt

Four profiles, built in, core the default

Profile · profile listpronto

Quatro profiles, embutidos, o core o padrão

~/example
# Every profile and its Nereids$ nereus profile listNAME                         NEREIDS                                                                                                                         INGRESS  DEFAULTcore                         -                                                                                                                               -        trueinternal-developer-platform  openbao, flux, cloudnative-pg, keycloak, nereus-portal, victoriametrics, vcluster, catalog, kubernetes, zot, buildkit, forgejo  istioreference                    reference-secrets, reference-release                                                                                            -secrets                      openbao                                                                                                                         -
Profile · profile describebuilt

What a profile installs, in the order of its images

Profile · profile describepronto

O que um profile instala, na ordem das suas imagens

~/example
# The Nereids, their reefs and Mandates, and who requires each$ nereus profile describe internal-developer-platformIngress: Gateway API v1.7.0, Istio 1.30.4 (Gateway istio-system/ingress) NEREID           REEF            MANDATE                    REQUIRED BYopenbao          secrets         default (default)          keycloak, forgejoflux             release         flux (default)             cloudnative-pg, keycloak, victoriametrics, vcluster, kubernetes, zot, forgejocloudnative-pg   database        cloudnative-pg (default)   keycloakkeycloak         authentication  keycloak (default)         nereus-portalnereus-portal    portal          nereus-portal (default)    -victoriametrics  metrics         victoriametrics (default)  -vcluster         environment     vcluster (default)         kubernetescatalog          catalog         catalog (default)          kubernetes, buildkitkubernetes       delivery        kubernetes (default)       -zot              registry        zot (default)              buildkitbuildkit         build           buildkit (default)         -forgejo          scm             forgejo (default)          -
Profile · profile applybuilt

A profile on top of core, from the laptop, one line per step

Profile · profile applypronto

Um profile sobre o core, do laptop, uma linha por passo

~/example
# Again, on a cluster that has it: every line unchanged$ nereus profile apply internal-developer-platform✓ reef secrets                    0.1s  core/reefs/secrets 0.1.0 unchanged (secrets.getnereus.dev/v1alpha1: secrets, secretbindings, vaults)✓ nereid openbao                  1.2s  core/nereids/openbao unchanged, Ready✓ mandate default                 0.0s  core/mandates/default unchanged (reef: secrets, nereid: openbao, default)✓ public key                      0.0s  rsa-4096, SHA256:szPWBVj2le3/W+vbmlx8oEAHRBvXP29a3qyYDM4LTnA, version 1✓ vault default                   0.0s  secrets/vaults/default unchanged (mandate: default)✓ reef release                    0.1s  core/reefs/release 0.1.0 unchanged (release.getnereus.dev/v1alpha1: releases, repositories, sources, targets)✓ flux                            0.6s  flux/v2.9.6 unchanged (source-controller, helm-controller in namespace flux-system)✓ nereid flux                     0.2s  core/nereids/flux unchanged, Ready✓ mandate flux                    0.0s  core/mandates/flux unchanged (reef: release, nereid: flux, default)✓ reef database                   0.0s  core/reefs/database 0.1.0 unchanged (database.getnereus.dev/v1alpha1: databases)✓ nereid cloudnative-pg           0.3s  core/nereids/cloudnative-pg unchanged, Ready✓ mandate cloudnative-pg          0.0s  core/mandates/cloudnative-pg unchanged (reef: database, nereid: cloudnative-pg, default)✓ reef authentication             0.0s  core/reefs/authentication 0.1.0 unchanged (authentication.getnereus.dev/v1alpha1: tokens)✓ nereid keycloak                 0.1s  core/nereids/keycloak unchanged, Ready✓ mandate keycloak                0.7s  core/mandates/keycloak unchanged (reef: authentication, nereid: keycloak, default)✓ gateway-api                     1.3s  gateway-api/v1.7.0 unchanged (the Gateway API CRDs)✓ repository istio                0.0s  release/repositories/istio unchanged✓ source istio-base               0.0s  release/sources/istio-base unchanged✓ source istiod                   0.0s  release/sources/istiod unchanged✓ source istio-gateway            0.0s  release/sources/istio-gateway unchanged✓ target istio-system             0.0s  release/targets/istio-system unchanged✓ release istio-base              0.7s  release/releases/istio-base unchanged (nereid: flux)✓ release istiod                  0.0s  release/releases/istiod unchanged (nereid: flux)✓ release istio-gateway           0.0s  release/releases/istio-gateway unchanged (nereid: flux)✓ gateway ingress                 0.0s  istio-system/ingress unchanged✓ reef portal                     0.0s  core/reefs/portal unchanged (portal.getnereus.dev/v1alpha1)✓ nereid nereus-portal            0.3s  core/nereids/nereus-portal unchanged, Ready✓ mandate nereus-portal           0.0s  core/mandates/nereus-portal unchanged (reef: portal, nereid: nereus-portal, default)✓ reef metrics                    0.0s  core/reefs/metrics unchanged (metrics.getnereus.dev/v1alpha1)✓ networkpolicy vmsingle-nereus   0.0s  networkpolicies/vmsingle-nereus applied (only vmagent-nereus and nereus-api reach vmsingle-nereus)✓ nereid victoriametrics          0.1s  core/nereids/victoriametrics unchanged, Ready✓ mandate victoriametrics         0.0s  core/mandates/victoriametrics unchanged (reef: metrics, nereid: victoriametrics, default)✓ reef environment                0.0s  core/reefs/environment 0.1.0 unchanged (environment.getnereus.dev/v1alpha1: environments)✓ nereid vcluster                 0.1s  core/nereids/vcluster unchanged, Ready✓ mandate vcluster                0.0s  core/mandates/vcluster unchanged (reef: environment, nereid: vcluster, default)✓ reef catalog                    0.1s  core/reefs/catalog unchanged (catalog.getnereus.dev/v1alpha1: packages, packagetypes, workloads, workloadtypes)✓ nereid catalog                  0.1s  core/nereids/catalog unchanged, Ready✓ mandate catalog                 0.0s  core/mandates/catalog unchanged (reef: catalog, nereid: catalog, default)✓ reef delivery                   0.0s  core/reefs/delivery unchanged (delivery.getnereus.dev/v1alpha1: deliveries)✓ nereid kubernetes               0.1s  core/nereids/kubernetes unchanged, Ready✓ mandate kubernetes              0.0s  core/mandates/kubernetes unchanged (reef: delivery, nereid: kubernetes, default)✓ reef registry                   0.0s  core/reefs/registry unchanged (registry.getnereus.dev/v1alpha1: registries, repositories)✓ nereid zot                      0.1s  core/nereids/zot unchanged, Ready✓ mandate zot                     0.0s  core/mandates/zot unchanged (reef: registry, nereid: zot, default)✓ reef build                      0.0s  core/reefs/build unchanged (build.getnereus.dev/v1alpha1: builds)✓ namespace builds                0.2s  namespaces/builds applied (Pod Security privileged, push credentials from the registry, the buildkit Nereid's Role, an admission policy on its Jobs and Pods, and one on Builds with no owner); namespaces/builds-egress applied (the egress proxy smokescreen, the only way out of a build's RUN)✓ nereid buildkit                 0.1s  core/nereids/buildkit unchanged, Ready✓ mandate buildkit                0.0s  core/mandates/buildkit unchanged (reef: build, nereid: buildkit, default)✓ reef scm                        0.0s  core/reefs/scm unchanged (scm.getnereus.dev/v1alpha1: connections, mirrors)✓ namespace nereus-system-forgejo 0.1s  namespaces/nereus-system-forgejo applied (the forgejo Nereid's Role there, for Forgejo's admin)✓ nereid forgejo                  0.1s  core/nereids/forgejo unchanged, Ready✓ mandate forgejo                 0.0s  core/mandates/forgejo unchanged (reef: scm, nereid: forgejo, default)  total                           6.4s Next steps:   nereus reef list  nereus nereid list
Config

Which settings does the platform keep?

Config

Quais configurações a plataforma guarda?

Config · config setbuilt

Your current owner, in the CLI's own config

Config · config setpronto

O seu owner atual, na config do próprio CLI

~/example
# The node the next commands are for$ nereus config set owner project/triton✓ config: owner = Project/triton
Config · config getbuilt

Read it back, with no cluster

Config · config getpronto

Leia de volta, sem cluster

~/example
# The current owner$ nereus config get ownerProject/triton # None set: the line says how$ nereus config get owner✗ owner is not set: nereus config set owner project/<name>
Config · config slo showbuilt

The SLO of init, from the cluster or its default

Config · config slo showpronto

O SLO do init, do cluster ou o seu padrão

~/example
# Each value and where it came from$ nereus config slo showSETTING    VALUE  SOURCElocal      8m     defaultcloud      20m    defaultyellow     50%    defaultorange     75%    defaultred        100%   defaulttolerance  20%    default
Config · config slo setbuilt

Change some values; the rest keep their defaults

Config · config slo setpronto

Mude alguns valores; o resto mantém o seu padrão

~/example
# A tighter objective on k3d, and a smaller tolerance$ nereus config slo set \    --local 4m \    --tolerance 5SETTING    VALUE  SOURCElocal      4m     clustercloud      20m    defaultyellow     50%    defaultorange     75%    defaultred        100%   defaulttolerance  5%     cluster
Config · config slo resetbuilt

Back to the defaults

Config · config slo resetpronto

De volta aos padrões

~/example
# Delete the SLO from the cluster$ nereus config slo reset✓ SLO reset: every value is back to its default
Config · config installation showbuilt

Every installation has a name, an id and an alias

Config · config installation showpronto

Toda instalação tem um nome, um id e um alias

~/example
# This installation$ nereus config installation showNAME            ALIAS           IDnereus-local  nereus-local  04d6e336-7dcb-42ab-926a-2595099d5336
Config · config installation setbuilt

Change the alias or a naming override; name and id stay

Config · config installation setpronto

Mude o alias ou um naming override; nome e id ficam

~/example
# A new alias$ nereus config installation set \    --alias "Acme Prod"✓ installation nereus-local  alias = Acme Prod✓ file ~/.config/nereus/init.yaml  updated # A name instead of a generated one that is taken$ nereus config installation set \    --naming-override issuer.storage=acmeissuers01✓ installation nereus-local  naming.overrides.issuer.storage = acmeissuers01✓ file ~/.config/nereus/init.yaml  updated
MCP

Which tools does claude.ai get?

MCP

Quais ferramentas o claude.ai recebe?

MCP · mcp tool listbuilt

The tools the reefs offer at /mcp, each on or off

MCP · mcp tool listpronto

As ferramentas que os reefs oferecem em /mcp, cada uma ligada ou desligada

~/example
# The tools you may call, the core's status first$ nereus mcp tool listREEF           TOOL                 STATEcore           status               onpresentations  presentations_list   onpresentations  presentations_share  off (write)
MCP · mcp tool enable | disablebuilt

An admin chooses which tools the instance offers

MCP · mcp tool enable | disablepronto

Um admin escolhe quais ferramentas a instância oferece

~/example
# Stop offering one tool$ nereus mcp tool disable presentations_list✓ tool presentations_list disabled for the instance # Offer every tool of a reef; the name above still wins$ nereus mcp tool enable 'presentations_*'✓ tools presentations_* enabled for the instance! presentations_list stays off: disabled by its own name, which beats a pattern
MCP · mcp client add | list | removebuilt

The instance's /mcp in Claude Code, with one command

MCP · mcp client add | list | removepronto

O /mcp da instância no Claude Code, com um comando

~/example
# Add the instance's MCP server to Claude Code$ nereus mcp client add claude-code✓ claude-code: MCP server nereus added (https://nereus.example.com/mcp, scope user, OAuth client claude-code) Next steps:   claude    # then /mcp, and log in to nereus # The coding agents that have it$ nereus mcp client listCLIENT       SERVER  URL                             SCOPEclaude-code  nereus  https://nereus.example.com/mcp  user