Kubernetes reference chart: no path for BReg migrations that need a --backup binding
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
- Área
- devops, documentation, infrastructure
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
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.pyrefuses the upgrade when the plan listsrequiredBackups(around line 49). The refusal is clean.templates/breg-operation-job.yamlbuilds thebregctl applyarguments 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:
- A values field for reviewed backup bindings (for example a list of
bindingPathand a file in a named, read-only claim or Secret), rendered as--backuparguments onplanandapply-successor, withstack_operator.pypassing them through instead of refusing. Tests intests/test_chart_contract.pyanddeploy/tests/test_operations.py. - 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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de registrystack/registry-stack
-
area:breg enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
registrystack/registry-stack#2765 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
registrystack/registry-stack#2761 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
registrystack/registry-stack#2743 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
registrystack/registry-stack#2706 ·
Los mantenedores suelen responder en 1 día
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
registrystack/registry-stack#2704 ·
Los mantenedores suelen responder en 1 día
Todos los issues de registrystack/registry-stack
Issues similares
-
help wanted needs investigation priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
[Bug] 建议把黑白主题设置同步到启动页面Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tomast1337/Puppeter-PptxGenJS#440 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
n0-computer/iroh#4709 ·
Los mantenedores suelen responder en 1 día
-
生词本里,已标记为认识的词,按钮写「不认识了」读着别扭Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
qingjian-team/qingjian#1114 ·
Los mantenedores suelen responder en 2 días