Kubernetes reference chart: no path for BReg migrations that need a --backup binding

Abierto
#2,754 0 comentarios 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
helm, kubernetes, python, rust

Línea de trabajo

Start at deploy/helm/registry-stack/README.md line 385 and the refusal in deploy/stack_operator.py line 49; then read the --backup argument construction in crates/registry-bregctl/src/lib.rs line 846 and deploy/helm/registry-stack/templates/breg-operation-job.yaml. Read tests/test_chart_contract.py and deploy/tests/test_operations.py for the chart/operator contract before choosing option 1 or 2. Done means either a values-driven backup binding rendered as --backup on plan and apply-successor with pass-through and tests, or a short deploy/OPERATIONS.md procedure for staging the file and running the Job by hand.

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

Descripción

area:breg enhancement

From the review of #2742, the Kubernetes reference chart under deploy/helm/registry-stack/. The chart is an unsupported reference (see its README), so this does not block anything.

What happens

A BReg successor whose plan lists requiredBackups cannot go through the chart:

  • deploy/stack_operator.py refuses the upgrade when the plan lists requiredBackups (around line 49). The refusal is clean.
  • templates/breg-operation-job.yaml builds the bregctl apply arguments with no way to pass --backup BINDING_PATH=BINDING_FILE (crates/registry-bregctl/src/lib.rs, around line 846).
  • The chart README (around line 385) sends the operator to the product procedure, which assumes a host shell. It does not say where the backup binding file is staged on Kubernetes or how the operation Job would read it.

So a destructive BReg migration on the reference deployment has no documented path.

Expected

One of:

  1. A values field for reviewed backup bindings (for example a list of bindingPath and a file in a named, read-only claim or Secret), rendered as --backup arguments on plan and apply-successor, with stack_operator.py passing them through instead of refusing. Tests in tests/test_chart_contract.py and deploy/tests/test_operations.py.
  2. Or, if that is too much for a reference, a short procedure in deploy/OPERATIONS.md: how to stage the binding file, run the operation Job by hand with --backup, and return to the guarded upgrade path.

Option 1 keeps the operator's reconcile-first rule in one place. Option 2 is smaller.

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
9 h 48 min
PR fusionados (30 d)
151

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 registrystack/registry-stack

Todos los issues de registrystack/registry-stack

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.