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 摘要。