Support rotating certs in running pods instead of restarting them
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- kubernetes, rust
研究方向
Start by tracing the CSIDriver configuration and the NodePublishVolume implementation, then find where the replace time is computed for the restarter annotation. The issue proposes opt-in per-volume certificate renewal, safe replacement of files in mounted volumes, and retaining restart behavior as a fallback. Done would include renewal on republish without exposing partially written certificates; the issue names no files or tests.
由索引模型根據 Issue 內容生成。
描述
Description
Right now, when a cert from the secret-operator gets close to expiring, the restarter just kills the pod based on the annotation set by secret-op (I think). That works, but it’s annoying for things that are slow to come back up or don't handle restarts well (looking at you, NiFi!), and it means short cert lifetimes come with a lot of restarts.
Some products can already reload certs from disk on their own. For example NiFi does this with nifi.security.autoreload.enabled. For products like that, it’d be nice if we could swap the cert in the volume and let the product take it from there, without forcing an unneeded restart on the pod.
The CSI lifecyle in Kubernetes has a hook for this: if we set requiresRepublish: true on our CSIDriver, the kubelet keeps calling NodePublishVolume for volumes that are already mounted. We can use that to check whether the cert is past its replace time and, if so, issue a new one and write it into the existing volume. We already compute that time for the restarter annotation, so we’d mainly need to keep it somewhere cheap to check, for example in memory with a small file in the volume as a fallback after the driver restarts.
This would have to be opt-in per volume, since products that don’t reload would just keep using the old cert until it expires. We’d probably also keep the restarter annotation as a safety net in case reissuing fails.
Bit of file handling to investigate since we don't want half-written certs being read, so probably need to come up with some symlink or mv magic, but that should be doable.
- 主要語言
- Rust
- 星號
- 14
- 分支
- 8
- 平均合併
- 1 天 12 小時
- 30 天內合併 PR
- 9
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
stackabletech/secret-operator 的其他 Issue
-
type/bug
難度 4/5 3-5 天 新手友好度 45/100
stackabletech/secret-operator#754 ·
維護者通常 1 天內回覆
-
autoTls: bound certificate lifetime by the CA that will actually sign it, not the configured caCertificateLifetime可能已有人在做 @xeniape 於 21 天前認領。 未關閉
難度 3/5 1-2 天 新手友好度 48/100
stackabletech/secret-operator#753 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
skip the PodListeners lookup when the served Pod is being deleted可能已有人在做 @soenkeliebau 於 5 天前認領。 未關閉
難度 3/5 1-2 天 新手友好度 72/100
stackabletech/secret-operator#720 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
customer-request type/bug
難度 3/5 1-2 天 新手友好度 38/100
stackabletech/secret-operator#666 · 2 則留言 ·
維護者通常 1 天內回覆
-
Allow certificates to contain subjects with allowed external names可能重新可做 @NickLarsenNZ 於 447 天前認領，目前沒有進行中的 PR。 未關閉customer-request type/feature-improvement
stackabletech/secret-operator#630 · 7 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 stackabletech/secret-operator 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 88/100
swc-project/swc-ai-issues#164 ·
-
難度 2/5 1-3 小時 新手友好度 85/100
pop-os/cosmic-player#367 ·
-
good first issue help wanted
難度 2/5 1-3 小時 新手友好度 72/100
servo/rust-smallvec#873 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
messense/dav-server-rs#82 ·
維護者通常 1 天內回覆