The authorization reef

Every command of the first slice: Users, teams, roles and bindings, and who may do what

O reef authorization

Todos os comandos da primeira fatia: Users, times, papéis e bindings, e quem pode fazer o quê

Opening · concepts

Three concepts, one list of members

  • User: the person, one in core, whatever the login
  • Team: who works together, each member with an optional position
  • Role and binding: what a team, a position or a User may do on a node of the tenancy tree
  • Access comes from the team: joining grants it, leaving removes it
Abertura · conceitos

Três conceitos, uma só lista de membros

  • User: a pessoa, uma só no core, qualquer que seja o login
  • Time: quem trabalha junto, cada membro com uma posição opcional
  • Papel e binding: o que um time, uma posição ou um User pode fazer em um nó da árvore de tenancy
  • O acesso vem do time: entrar concede, sair remove
Opening · the order

Who, may they, is there room: in this order

  • Who: authentication turns the token into a User
  • May they: authorization answers for a verb, a kind and a node
  • Is there room: quota, a later slice
Abertura · a ordem

Quem, pode, e há espaço: nesta ordem

  • Quem: authentication transforma o token em um User
  • Pode: authorization responde para um verbo, um kind e um nó
  • Há espaço: cota, uma fatia posterior
Setup

Where does the answer come from?

Preparação

De onde vem a resposta?

Setup · reef applybuilt #897

The authorization reef brings roles and bindings

Preparação · reef applypronto #897

O reef authorization traz papéis e bindings

~/example
# The kinds of the reef$ nereus reef apply authorization✓ core/reefs/authorization created (authorization.getnereus.dev/v1alpha1: bindings, roles) Next steps:   nereus nereid apply openfga --reef authorization
Setup · nereid applybuilt #897

openfga answers who may do what

Preparação · nereid applypronto #897

openfga responde quem pode fazer o quê

~/example
# The profile installs the Nereid and its default Mandate (an excerpt)$ nereus profile apply internal-developer-platform✓ networkpolicy openfga                      0.0s  networkpolicies/openfga applied (only nereus-api and vmagent-nereus reach openfga)✓ nereid openfga                            1m19s  core/nereids/openfga created, Ready✓ mandate openfga                            7.0s  core/mandates/openfga created (reef: authorization, nereid: openfga, default)
People

Who is on the platform, and with whom?

Pessoas

Quem está na plataforma, e com quem?

People · user createbuilt #897

A person is one User, whatever the login

Pessoas · user createpronto #897

Uma pessoa é um só User, qualquer que seja o login

~/example
# The tech lead$ nereus user create ana \    --email ana@example.com✓ core/users/ana created # A developer$ nereus user create bruno \    --email bruno@example.com✓ core/users/bruno created Next steps:   nereus teams create <team> --owner project/<project>
People · user listbuilt #897

Every User, and how many identities each has

Pessoas · user listpronto #897

Todo User, e quantas identidades cada um tem

~/example
# The people of this instance$ nereus user listNAME   EMAIL              IDENTITIES  AGEana    ana@example.com    1           2mbruno  bruno@example.com  0           1m
Roles

What can a role do?

Papéis

O que um papel pode fazer?

Roles · role listbuilt #897

One built-in role, three examples to edit

Papéis · role listpronto #897

Um papel embutido, três exemplos para editar

~/example
# The roles of this instance$ nereus authorization role listNAME           RULES                    BUILT INadministrator  *:*:*                    yesdeveloper      *:*:list,get and 3 more  -team-lead      *:*:list,get and 5 more  -viewer         *:*:list,get             -
Roles · role getbuilt #897

A role is a list of rules: reef, kinds, verbs

Papéis · role getpronto #897

Um papel é uma lista de regras: reef, kinds, verbos

~/example
# What a team lead may do$ nereus authorization role get team-leadteam-lead: 6 rulesREEF         KINDS         VERBS*            *             list,getbuild        builds        create,apply,deletedelivery     deliveries    create,apply,deleteenvironment  environments  create,deleterelease      releases      create,apply,deleteteams        members       create,delete
Roles · role createbuilt #897

A new role takes the words the CLI already uses

Papéis · role createpronto #897

Um papel novo usa as palavras que o CLI já usa

~/example
# A role of this instance's own$ nereus authorization role create release-manager \    --rule release:releases:create,apply,delete✓ authorization/roles/release-manager created Next steps:   nereus authorization binding create <name> --role release-manager --team <team> --owner project/<project>
Roles · role deletebuilt #897

The administrator role cannot be deleted

Papéis · role deletepronto #897

O papel administrator não pode ser apagado

~/example
# No one locks the instance out$ nereus authorization role delete administrator✗ authorization/roles/administrator is built in: it cannot be changed or deleted. To see who holds it, run:  nereus authorization binding list --role administrator  Nothing was changed.
Bindings

Who receives a role, and where?

Bindings

Quem recebe um papel, e onde?

Bindings · binding createbuilt #897

A binding gives a role to a team on a node

Bindings · binding createpronto #897

Um binding dá um papel a um time em um nó

~/example
# Everyone in the team is a developer of the Project$ nereus authorization binding create payments-developers \    --role developer \    --team payments \    --owner project/payments✓ authorization/bindings/payments-developers created Next steps:   nereus authorization binding list --owner project/payments
Bindings · binding createbuilt #897

A position narrows the binding to the tech lead

Bindings · binding createpronto #897

Uma posição restringe o binding ao tech lead

~/example
# Only who holds the position$ nereus authorization binding create payments-leads \    --role team-lead \    --team payments \    --position tech-lead \    --owner project/payments✓ authorization/bindings/payments-leads created Next steps:   nereus authorization binding list --owner project/payments
Bindings · binding listbuilt #897

Every binding of a node, and who it reaches

Bindings · binding listpronto #897

Todo binding de um nó, e quem ele alcança

~/example
# Who may do what on the Project$ nereus authorization binding list \    --owner project/paymentsNAME                 SUBJECT                  ROLE       OWNERpayments-developers  team/payments            developer  project/paymentspayments-leads       team/payments/tech-lead  team-lead  project/payments
Asking

May I?

Perguntando

Eu posso?

Asking · can-ibuilt #897

Ana asks, and the answer names the binding

Perguntando · can-ipronto #897

A Ana pergunta, e a resposta cita o binding

~/example
# Signed in as ana: with no --user, the question is about the caller$ nereus authorization can-i create environment/environments \    --owner project/paymentsyes: authorization/bindings/payments-leads gives team-lead to team/payments/tech-lead at project/payments
Asking · can-i --userbuilt #897

Bruno may not, and the answer says why

Perguntando · can-i --userpronto #897

O Bruno não pode, e a resposta diz por quê

~/example
# About someone else$ nereus authorization can-i create environment/environments \    --owner project/payments \    --user brunono: no binding gives bruno create on environment/environments at project/payments Next steps:   nereus authorization binding list --owner project/payments
Asking · can-ibuilt #897

The shortcut asks the same question

Perguntando · can-ipronto #897

O atalho faz a mesma pergunta

~/example
# Signed in as bruno: a developer creates builds$ nereus can-i create build/builds \    --owner project/paymentsyes: authorization/bindings/payments-developers gives developer to team/payments at project/payments
Asking · can-i drivebuilt #1726

Presenting is a right: a Session's speakers drive it

Perguntando · can-i drivepronto #1726

Apresentar é um direito: os speakers de uma Session a conduzem

~/example
# Ana is a speaker of platform-day$ nereus authorization can-i drive presentations/sessions/platform-day \    --user anayes: ana is a speaker of platform-day # Bruno is not$ nereus authorization can-i drive presentations/sessions/platform-day \    --user brunono: bruno is not a speaker of platform-day, and no binding gives bruno drive on presentations/sessions Next steps:   nereus presentations session get platform-day  nereus authorization binding list
Asking · can-i assistbuilt #1727

The staff assists a Session, and never drives it

Perguntando · can-i assistpronto #1727

O staff acompanha uma Session, e nunca a conduz

~/example
# Carla is on the staff team of platform-day$ nereus authorization can-i assist presentations/sessions/platform-day \    --user carlayes: carla is on the staff of platform-day (team stage-2-staff) # Ana drives it, so she assists it too$ nereus authorization can-i assist presentations/sessions/platform-day \    --user anayes: ana is a speaker of platform-day # Bruno is neither$ nereus authorization can-i assist presentations/sessions/platform-day \    --user brunono: bruno is neither a speaker nor on the staff of platform-day, and no binding gives bruno assist on presentations/sessions Next steps:   nereus presentations session get platform-day  nereus authorization binding list
Enforcement

What happens when the answer is no?

Na prática

O que acontece quando a resposta é não?

Enforcement · environment createbuilt #897

Bruno's environment is refused, politely

Na prática · environment createpronto #897

O ambiente do Bruno é recusado, com educação

~/example
# Signed in as bruno$ nereus environment create staging \    --owner project/payments✗ environment/environments/staging: bruno may not create environment/environments at project/payments. To see who may, run:  nereus authorization binding list --owner project/payments  Nothing was changed.
Enforcement · environment createbuilt #897

Ana's environment is created

Na prática · environment createpronto #897

O ambiente da Ana é criado

~/example
# Signed in as ana, the tech lead$ nereus environment create staging \    --owner project/payments✓ environment/environments/staging created (mandate: vcluster, nereid: vcluster) Next steps:   nereus environment get staging --watch
Enforcement · member deleteplanned #1307

Leaving the team removes the access

Na prática · member deleteplanejado #1307

Sair do time remove o acesso

~/example
# Ana leaves the team$ nereus teams member delete ana \    --team payments✓ teams/teams/payments/members/ana deleted # And the answer changes with her$ nereus authorization can-i create environment/environments \    --owner project/payments \    --user anano: no binding gives ana create on environment/environments at project/payments
Enforcement · fail closedbuilt #897

Without openfga, everything closes

Na prática · fecha tudopronto #897

Sem openfga, tudo se fecha

~/example
# A read while the Nereid does not answer$ nereus environment list✗ authorization does not answer (nereid: openfga): nothing is allowed until it is back. To see what is down, run:  nereus doctor  Nothing was changed. # What stays open says why$ nereus doctorCHECK           RESULT  DETAILapi             pass    answerednereids         fail    13 of 14 Ready, not Ready: openfga (Unavailable)emergency-exit  warn    nereus-admins passed through the emergency exit 199 times since the API started, the last less than a minute ago by admin: give the administrators their own User and a binding of administrator
Closing · later

Out of this slice, each with its next step

  • A second identity: linked to the same User after an e-mail code
  • Agents as subjects: acting for a person, with the same access or less
  • Quotas: per Organization, Project and team
  • Kubernetes RBAC: bindings projected into the namespaces
  • Position as a kind: with its skills and places
  • Identity provider groups: written from the teams, never read
Fechamento · depois

Fora desta fatia, cada um com o seu próximo passo

  • Uma segunda identidade: ligada ao mesmo User depois de um código por e-mail
  • Agentes como sujeitos: agindo por uma pessoa, com o mesmo acesso ou menos
  • Cotas: por Organization, Project e time
  • RBAC do Kubernetes: bindings projetados nos namespaces
  • Position como kind: com as suas skills e vagas
  • Grupos do provedor de identidade: escritos a partir dos times, nunca lidos
References

Sources

Referências

Fontes

References · 1/3

OpenFGA

The OpenFGA Authors, a CNCF project

  • About: An open source authorization engine based on relationships, inspired by Google's Zanzibar: a model of types and relations, tuples that say who relates to what, and a check that answers yes or no.
  • For this talk: The Nereid of this reef: it keeps the tuples the roles, bindings and teams turn into, and answers every check the Nereus API asks.
Referências · 1/3

OpenFGA

The OpenFGA Authors, a CNCF project

  • Sobre: Um motor de autorização de código aberto baseado em relações, inspirado no Zanzibar do Google: um modelo de tipos e relações, tuplas que dizem quem se relaciona com o quê, e uma verificação que responde sim ou não.
  • Para esta palestra: A Nereid deste reef: guarda as tuplas em que os papéis, bindings e times se transformam, e responde a toda verificação que a Nereus API pergunta.

https://openfga.dev/

References · 2/3

Using RBAC Authorization

The Kubernetes Authors

  • About: Kubernetes' role-based access control: a Role lists rules (API groups, resources, verbs) and a RoleBinding grants it to subjects.
  • For this talk: The shape of a role's rule here, in the CLI's own words: reef, kinds, verbs.
Referências · 2/3

Using RBAC Authorization

The Kubernetes Authors

  • Sobre: O controle de acesso baseado em papéis do Kubernetes: um Role lista regras (grupos de API, recursos, verbos) e um RoleBinding o concede a sujeitos.
  • Para esta palestra: A forma da regra de um papel aqui, nas palavras do próprio CLI: reef, kinds, verbos.

https://kubernetes.io/docs/reference/access-authn-authz/rbac/

References · 3/3

Thinking in Platforms

Kaspar von Grünberg and Luca Galante · 2026

  • About: Platform engineering as the operating model for work in the AI era.
  • For this talk: The order of the checks: identity, team membership and resource quotas are resolved before any path is invoked.
Referências · 3/3

Thinking in Platforms

Kaspar von Grünberg and Luca Galante · 2026

  • Sobre: Engenharia de plataforma como o modelo operacional do trabalho na era da IA.
  • Para esta palestra: A ordem das verificações: identidade, participação em times e cotas de recursos são resolvidas antes de qualquer caminho ser invocado.

https://internaldeveloperplatform.org/community/books/