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

オープン
#2,754 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
48/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
helm, kubernetes, python, rust

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
2
フォーク
0
平均マージ
9時間 48分
マージ済み PR(30日)
151

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

registrystack/registry-stack のほかの issue

registrystack/registry-stack の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。