How do I install the Debug Csi skill?

Run npx skillmds@latest add kubernetes-sigs/debug-csi in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Debug Csi safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Debug Csi?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Debug Csi free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Debug Csi?

kubernetes-sigs (@kubernetes-sigs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Debug Csi by kubernetes-sigs — Agent Skill

Name: Debug Csi
Author: kubernetes-sigs

Debug Csi

Build, deploy, and debug the alibaba-cloud-csi-driver on a test cluster. Use this skill when the user wants to build images, deploy via helm, check logs, restart components, or troubleshoot the CSI plugin/provisioner. Also trigger for "deploy csi", "check csi logs", "restart csi", "debug csi", "build and push", or any question about how to iterate on this driver in a dev cluster.

kubernetes-sigs f68268c 7 files · 12.2 KB Updated Sep 17, 2026

File contents

Debug CSI Driver

This skill covers the build-deploy-debug loop for the CSI driver on an ACK test cluster.

Prerequisite: .local/test-values.yaml must exist. If it doesn't (or the cluster it refers to is unreachable), run /init-dev-env first.

Build and deploy

Uninstall component-center version (if present)

Before deploying via helm, check whether the CSI driver was installed via the ACK component center:

helm list -n kube-system

If there's a csi release, it's already a debug version — skip uninstall. Otherwise run:

../../init-dev-env/scripts/uninstall-csi-addon.sh

Build and push images

When building from a non-VPC environment (e.g. local machine), apply the yum mirror patch first so that container builds can access Alinux repos:

git apply .agents/skills/debug-csi/yum-mirror.diff

This is a local-only patch — do not commit it. Just revert it if it gets into your way, and apply it again when building again.

PLATFORM=linux/amd64 IMAGE_REPO=<registry>/<namespace> IMAGE_TAG=latest ./build/build-all-multi.sh

Refer to .local/test-values.yaml for the registry and namespace. IMAGE_TAG defaults to latest; set it to a custom tag (e.g. v1.35.3-dev) if needed. The script builds and pushes all images: csi-plugin, csi-plugin:init, csi-plugin:controller, csi-agent, csi-ossfs, csi-ossfs2, csi-alinas, mount-proxy.

To build only specific images, set IMAGES (space-separated names without tags):

IMAGES="mount-proxy csi-agent" PLATFORM=linux/amd64 IMAGE_REPO=<registry>/<namespace> ./build/build-all-multi.sh

Deploy via helm

helm upgrade -f .local/test-values.yaml -n kube-system ack-csi-plugin ./deploy/charts/alibaba-cloud-csi-driver
# One-time: set imagePullPolicy to Always
scripts/set-image-pull-policy.sh

If only images changed (no chart changes), rolling-restart instead of helm upgrade:

kubectl -n kube-system rollout restart deploy/csi-provisioner
kubectl -n kube-system rollout restart daemonset/csi-plugin

Debugging and logs

csi-plugin (daemonset, runs on each node, handles NodePublish/NodeUnpublish):

kubectl -n kube-system logs -l app=csi-plugin -c csi-plugin --tail=100

csi-provisioner (deployment, handles ControllerPublish/ControllerUnpublish):

kubectl -n kube-system logs -l app=csi-provisioner -c csi-provisioner --tail=100

Restarting components

Patching the pod template (env, imagePullPolicy, etc.) automatically triggers a rolling update. rollout restart is only needed when the patch reports "no change" (e.g. image tag is the same).

Test pod images

Use mirrors-ssl.aliyuncs.com/busybox or mirrors-ssl.aliyuncs.com/debian as test pod images. Also use these for ephemeral containers and kubectl debug commands. Docker Hub and other registries outside China are unreliable due to network issues. mirrors-ssl.aliyuncs.com mirrors all popular official Docker Hub images.

OSS / OSSFS

For OSSFS-related debugging (fuse pod image config, fuse pod logs, fuse pod lifecycle), read references/oss.md.

NAS / cnfs-nas-daemon

For NAS mount proxy debugging (enabling the proxy, testing cnfs-nas-daemon images, EFC mount flow), read references/nas.md.

---name: debug-csidescription: Build, deploy, and debug the alibaba-cloud-csi-driver on a test cluster. Use this skill when the user wants to build images, deploy via helm, check logs, restart components, or troubleshoot the CSI plugin/provisioner. Also trigger for "deploy csi", "check csi logs", "restart csi", "debug csi", "build and push", or any question about how to iterate on this driver in a dev cluster.---# Debug CSI DriverThis skill covers the build-deploy-debug loop for the CSI driver on an ACK test cluster.Prerequisite: `.local/test-values.yaml` must exist. If it doesn't (or the cluster it refers to is unreachable), run `/init-dev-env` first.## Build and deploy### Uninstall component-center version (if present)Before deploying via helm, check whether the CSI driver was installed via the ACK component center:```bashhelm list -n kube-system```If there's a `csi` release, it's already a debug version — skip uninstall. Otherwise run:```bash../../init-dev-env/scripts/uninstall-csi-addon.sh```### Build and push imagesWhen building from a non-VPC environment (e.g. local machine), apply the yum mirror patch first so that container builds can access Alinux repos:```bashgit apply .agents/skills/debug-csi/yum-mirror.diff```This is a local-only patch — do not commit it. Just revert it if it gets into your way, and apply it again when building again.```bashPLATFORM=linux/amd64 IMAGE_REPO=<registry>/<namespace> IMAGE_TAG=latest ./build/build-all-multi.sh```Refer to `.local/test-values.yaml` for the registry and namespace.`IMAGE_TAG` defaults to `latest`; set it to a custom tag (e.g. `v1.35.3-dev`) if needed.The script builds and pushes all images: `csi-plugin`, `csi-plugin:init`, `csi-plugin:controller`, `csi-agent`, `csi-ossfs`, `csi-ossfs2`, `csi-alinas`, `mount-proxy`.To build only specific images, set `IMAGES` (space-separated names without tags):```bashIMAGES="mount-proxy csi-agent" PLATFORM=linux/amd64 IMAGE_REPO=<registry>/<namespace> ./build/build-all-multi.sh```### Deploy via helm```bashhelm upgrade -f .local/test-values.yaml -n kube-system ack-csi-plugin ./deploy/charts/alibaba-cloud-csi-driver# One-time: set imagePullPolicy to Alwaysscripts/set-image-pull-policy.sh```If only images changed (no chart changes), rolling-restart instead of helm upgrade:```bashkubectl -n kube-system rollout restart deploy/csi-provisionerkubectl -n kube-system rollout restart daemonset/csi-plugin```## Debugging and logs**csi-plugin** (daemonset, runs on each node, handles NodePublish/NodeUnpublish):```bashkubectl -n kube-system logs -l app=csi-plugin -c csi-plugin --tail=100```**csi-provisioner** (deployment, handles ControllerPublish/ControllerUnpublish):```bashkubectl -n kube-system logs -l app=csi-provisioner -c csi-provisioner --tail=100```## Restarting componentsPatching the pod template (env, imagePullPolicy, etc.) automatically triggers a rolling update.`rollout restart` is only needed when the patch reports "no change" (e.g. image tag is the same).## Test pod imagesUse `mirrors-ssl.aliyuncs.com/busybox` or `mirrors-ssl.aliyuncs.com/debian` as test pod images.Also use these for ephemeral containers and `kubectl debug` commands.Docker Hub and other registries outside China are unreliable due to network issues.`mirrors-ssl.aliyuncs.com` mirrors all popular official Docker Hub images.## OSS / OSSFSFor OSSFS-related debugging (fuse pod image config, fuse pod logs, fuse pod lifecycle), read `references/oss.md`.## NAS / cnfs-nas-daemonFor NAS mount proxy debugging (enabling the proxy, testing cnfs-nas-daemon images, EFC mount flow), read `references/nas.md`.

Frequently asked questions