From 69c90b9fdfc307df5135e2a8585ff13253cfa0ed Mon Sep 17 00:00:00 2001 From: panxiao81 Date: Mon, 21 Sep 2026 12:33:35 +0000 Subject: [PATCH] =?UTF-8?q?fix:=20=E4=B8=BA=20Kata=20kind=20executor=20?= =?UTF-8?q?=E9=85=8D=E7=BD=AE=E6=9C=80=E4=BD=8E=E8=B5=84=E6=BA=90?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- platform/sandbox-ci-runners/README.md | 4 ++++ platform/sandbox-ci-runners/pools.yaml | 7 +++++++ 2 files changed, 11 insertions(+) diff --git a/platform/sandbox-ci-runners/README.md b/platform/sandbox-ci-runners/README.md index 8c47502..f77c7aa 100644 --- a/platform/sandbox-ci-runners/README.md +++ b/platform/sandbox-ci-runners/README.md @@ -14,6 +14,10 @@ VM 与 Pod backend 使用同一个 `gitea-dynamic-runner-runner` executor 镜像 daemon。Kata VM 中的 workflow 必须先把稀疏 ext4 镜像 loop-mount 到 `/var/lib/docker`，并完成 cgroup v2 nesting 初始化。 +`ci-vm` executor 固定请求并限制为 2 CPU/3GiB。真实 kind canary 表明 1 CPU/约 2GiB +虽然能最终启动全部 control-plane 容器，但无法在 kubeadm 超时前提供可用的 API server； +该规格是 nested Kubernetes 任务的容量下限，不是用资源掩盖存储阻塞。 + 这些 `ClusterStaticEntry` 位于 sandbox 集群，由 central SPIRE Server 内的 `spire-controller-manager-sandbox` 通过受限 external kubeconfig reconcile。必须在 `platform/spire/values.yaml` 显式启用 external controller-manager 的 diff --git a/platform/sandbox-ci-runners/pools.yaml b/platform/sandbox-ci-runners/pools.yaml index 6645bd5..a564347 100644 --- a/platform/sandbox-ci-runners/pools.yaml +++ b/platform/sandbox-ci-runners/pools.yaml @@ -74,6 +74,13 @@ spec: runAsNonRoot: true runAsUser: 2000 runAsGroup: 2000 + resources: + requests: + cpu: "2" + memory: 3Gi + limits: + cpu: "2" + memory: 3Gi volumeMounts: - name: opensandbox-bin mountPath: /opt/opensandbox -- 2.54.0