Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Cluster upgrade test failed

未关闭
#562 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
helm, kubernetes

调研方向

Start by reproducing the failed Helm upgrade for the pulsar-ci cluster and inspect the generated pulsar-ci-zookeeper StatefulSet. Compare the existing and upgraded specs to identify the field outside replicas, template, and updateStrategy that changes. Done means the cluster upgrade completes without the Kubernetes immutable-spec error.

由索引模型根据 Issue 内容生成。

描述

Exception:

client.go:181: [debug] error updating the resource "pulsar-ci-zookeeper":
	 cannot patch "pulsar-ci-zookeeper" with kind StatefulSet: StatefulSet.apps "pulsar-ci-zookeeper" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden
client.go:170: [debug] Created a new Ingress called "pulsar-ci-control-center-ingress" in pulsar

upgrade.go:280: [debug] warning: Upgrade "pulsar-ci" failed: cannot patch "pulsar-ci-zookeeper" with kind StatefulSet: StatefulSet.apps "pulsar-ci-zookeeper" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden
Error: UPGRADE FAILED: cannot patch "pulsar-ci-zookeeper" with kind StatefulSet: StatefulSet.apps "pulsar-ci-zookeeper" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden
helm.go:76: [debug] cannot patch "pulsar-ci-zookeeper" with kind StatefulSet: StatefulSet.apps "pulsar-ci-zookeeper" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden
主要语言
Go Template
星标
80
派生
69
平均合并
21 小时 23 分钟
30 天内合并 PR
1

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

streamnative/charts 的其他 Issue

查看 streamnative/charts 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。