jenkins通过pipeline方式发布到k8s，pod一直起不来

[wsw136]

What happened? 发生了什么问题？

Feb 23 11:35:30 kubeadm-node-t03 kubelet[31216]: I0223 11:35:30.849322 31216 reconciler.go:253] "operationExecutor.MountVolume started for volume \"kube-api-access-jlgzd\" (UniqueName: \"kubernetes.io/projected/9f490671-1730-4c7c-8224-a5474bc4a44b-kube-api-access-jlgzd\") pod \"adpt-baiwang-static-59f8fd8bf9-xxhb6\" (UID: \"9f490671-1730-4c7c-8224-a5474bc4a44b\") " pod="demo/adpt-baiwang-static-59f8fd8bf9-xxhb6" Feb 23 11:35:30 kubeadm-node-t03 kubelet[31216]: E0223 11:35:30.868723 31216 atomic_writer.go:391] pod demo/adpt-baiwang-static-59f8fd8bf9-xxhb6 volume kube-api-access-jlgzd: unable to write file /var/lib/kubelet/pods/9f490671-1730-4c7c-8224-a5474bc4a44b/volumes/kubernetes.io~projected/kube-api-access-jlgzd/..2024_02_23_03_35_30.2508898893/ca.crt with mode -rw-r--r--: write /var/lib/kubelet/pods/9f490671-1730-4c7c-8224-a5474bc4a44b/volumes/kubernetes.io~projected/kube-api-access-jlgzd/..2024_02_23_03_35_30.2508898893/ca.crt: no space left on device Feb 23 11:35:30 kubeadm-node-t03 kubelet[31216]: E0223 11:35:30.868779 31216 atomic_writer.go:178] pod demo/adpt-baiwang-static-59f8fd8bf9-xxhb6 volume kube-api-access-jlgzd: error writing payload to ts data directory /var/lib/kubelet/pods/9f490671-1730-4c7c-8224-a5474bc4a44b/volumes/kubernetes.io~projected/kube-api-access-jlgzd/..2024_02_23_03_35_30.2508898893: write /var/libkubelet/pods/9f490671-1730-4c7c-8224-a5474bc4a44b/volumes/kubernetes.io~projected/kube-api-access-jlgzd/..2024_02_23_03_35_30.2508898893/ca.crt: no space left on device Feb 23 11:35:30 kubeadm-node-t03 kubelet[31216]: E0223 11:35:30.868803 31216 projected.go:236] Error writing payload to dir: write /var/lib/kubelet/pods/9f490671-1730-4c7c-8224-a5474bc4a44b/volumes/kubernetes.io~projected/kube-api-access-jlgzd/..2024_02_23_03_35_30.2508898893/ca.crt: no space left on device Feb 23 11:35:30 kubeadm-node-t03 kubelet[31216]: E0223 11:35:30.882185 31216 nestedpendingoperations.go:335] Operation for "{volumeName:kubernetes.io/projected/9f490671-1730-4c7c-8224-a5474bc4a44b-kube-api-access-jlgzd podName:9f490671-1730-4c7c-8224-a5474bc4a44b nodeName:}" failed. No retries permitted until 2024-02-23 11:36:34.882145251 +0800 CST m=+237198.638006451 (durationBeforeRetry 1m4s). Error: MountVolume.SetUp failed for volume "kube-api-access-jlgzd" (UniqueName: "kubernetes.io/projected/9f490671-1730-4c7c-8224-a5474bc4a44b-kube-api-access-jlgzd") pod "adpt-baiwang-static-59f8fd8bf9-xxhb6" (UID: "9f490671-1730-4c7c-8224-a5474bc4a44b") : write /var/lib/kubelet/pods/9f490671-1730-4c7c-8224-a5474bc4a44b/volumes/kubernetes.io~projected/kube-api-access-jlgzd/..2024_02_23_03_35_30.2508898893/ca.crt: no space left on device

What did you expect to happen? 期望的结果是什么？

我需要通过pipeline方式部署使正常pod跑起来

How can we reproduce it (as minimally and precisely as possible)? 尽可能最小化、精确地描述如何复现问题

jenkins通过pipeline方式发布到k8s，pod一直起不来

Anything else we need to know? 其他需要说明的情况

No response

Kubernetes version k8s 版本

v1.23.1

Kubeasz version

kubeasz-3.2.0

OS version 操作系统版本

```console # On Linux: $ cat /etc/os-release # centos 7.6 $ uname -a # 3.10.0-957.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC 2018 x86_64 x86_64 x86_64 ```

Related plugins (CNI, CSI, ...) and versions (if applicable) 其他网络插件等需要说明的情况

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.