Support native sidecar containers in the Pod builder(s)

未關閉
#1,317 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
62/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
kubernetes, rust
領域
tooling

研究方向

Start in the builder code around ContainerBuilder and PodBuilder::add_init_container; the issue names both entry points and the default-resource behavior to change. Read how init containers currently receive default limits, then expose restartPolicy and make it possible to add a native sidecar without those defaults. Done means a builder-created init container can use restartPolicy: Always without the 10m CPU / 128Mi memory defaults, with builder tests covering the new path.

由索引模型根據 Issue 內容生成。

描述

Problem

The builders have no way to add a native sidecar (init container with restartPolicy: Always). ContainerBuilder doesn't expose restartPolicy, and PodBuilder::add_init_container sets default limits of 10m CPU / 128Mi memory on any init container without resources. Those defaults apparently exist for ResourceQuota support (stackabletech/issues#368) and are probably fine for one-shot init containers but also probably not for Vector et.al.

Scope

Adding a native sidecar through the builders, without the init-container resource defaults.

Expected effort

1 day. If it takes longer, stop and flag it.

Out of scope

  • Moving any existing sidecar (Vector, git-sync, ...) over to it.
  • The container-type / default-resources refactor the FIXME in add_init_container asks for.
主要語言
Rust
星號
170
分支
20
平均合併
2 天 12 小時
30 天內合併 PR
24

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

stackabletech/operator-rs 的其他 Issue

查看 stackabletech/operator-rs 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。