🤖 Operator token record: residual limits after #428

Abierto
  • ¿Algo no está bien?
#432 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go, kubernetes
Área
backend, databases

Línea de trabajo

Read PR #428 and the linked discussion threads for each item to locate the reconcile code writing status.operatorAccessReady and operatorTokenSecretRef. Check docs/how-to/deploy-controller.md for the hash/URL item. Done means each listed residual limit is fixed with live readiness writes and a recorded database identity.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Follow-ups that PR #428 (fix for #406) leaves open. Each one needs more than a small change in the operator token record, so #428 documents it or leaves it here.

  1. Readiness during a database change. When a ready control plane moves to a database with another hash, status.operatorAccessReady stays true, with the old status.operatorTokenSecretRef, until the final status write of that reconcile. This matches main. During that window, consumers send the old token to the new database and get 401s at the control plane origin. No token goes to another origin. A fix sets readiness to false in the record write before the create. It also needs a live write that restores readiness, because the final status write merges only the fields that changed against the first read of the reconcile. Codex thread: https://github.com/coder/coder-k8s/pull/428#discussion_r4429874209
  2. Secret rename on a record from an earlier version. When an upgraded control plane has a record without status.operatorTokenID and spec.operatorAccess.generatedTokenSecretName changes, the rotation deletes the old token and writes the new one only to the renamed Secret. If the final status write fails, or the controller stops, status still names the old Secret with operatorAccessReady=true, so consumers get 401s until the next reconcile. This matches main, where a rename also always rotates because the renamed Secret is empty. The fix is the same live readiness write as item 1. Codex thread: https://github.com/coder/coder-k8s/pull/428#discussion_r4430006050
  3. One record per control plane. When a control plane that owns its Secret moves to another database, the controller records the new database before it provisions there. It then no longer deletes a token in the earlier database. main also forgot that token. Keeping the old record would block operator access after every URL change. A fix needs a second record (a status field) and a way to reach the old database.
  4. The hash names a URL, not a server (#406 item 5, documented in docs/how-to/deploy-controller.md). A sound fix records a database identity read from the server, for example Coder's deployment ID, and checks it inside the delete transaction.
  5. --cascade=orphan (#406 item 3, documented). Readers cannot tell an orphaned Secret from a replaced one without a record of the Secret's UID.

Not in scope here: a record from a create that failed before its commit no longer authorizes a delete by name. #428 fixes that case with status.operatorTokenID.

Trigger: the next change to operator access, or a report of a token that stayed valid or was deleted in the wrong database.

Refs #406, #428

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: xhigh

Lenguaje dominante
Go
Estrellas
5
Forks
3
Merge medio
2 h 49 min
PR fusionados (30 d)
206

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de coder/coder-k8s

Todos los issues de coder/coder-k8s

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.