kubesphere-openkruise
KubeSphere OpenKruise management Skill. Use when user asks to install or enable OpenKruise, check OpenKruise status, view kruise pods/logs/CRDs, create or update SidecarSet, manage sidecar injection, create or update CloneSet, perform in-place update or batch rollout, uninstall or remove OpenKruise, or troubleshoot Kruise Pod, CRD, and webhook issues in KubeSphere.
npx skills add kubesphere/kubesphere --skill kubesphere-openkruise --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Instructs the agent to manage the OpenKruise extension within KubeSphere: install or upgrade via InstallPlan, query status/CRDs/pods/logs, generate SidecarSet and CloneSet manifests for injection and workload updates, uninstall the extension, and troubleshoot Kruise Pods, CRDs, and webhooks. It explicitly covers installing, querying, generating manifests, uninstalling, and troubleshooting OpenKruise in KubeSphere.
How it works
The skill provides step-by-step guidance and concrete YAML or kubectl/ks API outputs for:
- Verifying extension existence and exact version before producing InstallPlan, preferring extension version 1.0.3 when not otherwise provided in this environment.
- Preparing an InstallPlan YAML with spec.extension.name, spec.extension.version, upgradeStrategy: Manual, and clusterScheduling placement (host, member-4, etc.).
- Applying the InstallPlan and monitoring installation status via kubectl get/installplan and kubectl describe installplan, then checking extension status.
- Ensuring discovery of API versions prior to generating SidecarSet or CloneSet manifests by inspecting kubectl api-resources from apps.kruise.io.
- Managing SidecarSet and CloneSet lifecycle with provided templates or generated manifests, including common kubectl apply/get/describe/delete flows and verification steps for injection and updates.
- Providing commands to view extension versions, extension details, and Kruise CRDs, pods, and hooks.
- Uninstalling OpenKruise with caution about CRDs and existing configurations, and warning about potential removal of app configurations.
When to use it
Use when the user asks to install or enable OpenKruise, check status, view Kruise resources or logs, create or update SidecarSet or CloneSet, perform in-place updates or batch rollouts, uninstall, or troubleshoot Kruise-related issues in KubeSphere.
What it can touch
- InstallPlan objects (cluster-scoped)
- SidecarSet and CloneSet manifests and resources (apps.kruise.io)
- OpenKruise extension and extensionversion resources
- Kruise system pods, CRDs, and related resources
- kubectl and KubeSphere API calls as described in the guidance
Caveats
- Out of scope by default for deep OpenKruise CRDs not requested (e.g., BroadcastJob, UnitedDeployment, etc.) and deep chart-value design without cluster evidence. Follow-up tasks should be used for those.
- Version handling rules require verification: if the runtime OpenKruise version is provided but not the matching extension version, the user is asked to confirm the mapping; never invent a version. If missing, show how to list versions and ask for confirmation.
- InstallPlan is cluster-scoped and name must align with the extension name in metadata.
- Upgrade strategy defaults to Manual unless requested otherwise.
# Skill: kubesphere-openkruise # KubeSphere OpenKruise Management Use this skill for the full OpenKruise lifecycle in KubeSphere: - Install or upgrade the OpenKruise extension through `InstallPlan` - Query extension status, CRDs, Pods, and logs - Generate `SidecarSet` manifests for sidecar injection and rolling updates - Generate `CloneSet` manifests for advanced stateless workloads, in-place updates, and batch rollout - Uninstall the OpenKruise extension - Troubleshoot failed Pods, missing CRDs, and webhook problems Out of scope by default: - Advanced OpenKruise CRDs not requested by the user, such as `BroadcastJob`, `NodeImage`, `UnitedDeployment`, or `AdvancedPodAutoscaler` - Deep chart-value design without cluster evidence If the user explicitly asks for those CRDs, acknowledge that they are OpenKruise capabilities but treat them as a follow-up task instead of assuming they belong in the default workflow. ## Response Rules - Prefer executable output: `InstallPlan` YAML, `SidecarSet` YAML, `CloneSet` YAML, `kubectl` commands, or a short ordered procedure. - Verify the extension name and exact version before generating a final `InstallPlan`. - Default the extension name to `openk
- Response Rules
- Version Mapping Discovery
- Discovery Commands
- Option 1: Using KubeSphere API (curl)
- Multi-Cluster Resource Query (host cluster)
- Multi-Cluster Resource Query (member cluster)
- Option 2: Using kubectl (Direct Cluster Access)
- Option 3: Multi-Cluster Query (kubeconfig extraction)
- When to Use Which Approach
- Install OpenKruise in KubeSphere
- 1. Pre-check
- 2. InstallPlan Template
- 2.1 Config Handling
- 3. Status and Logs After Install
kubectl api-resources --api-group apps.kruise.io
Discover KubeSphere extension version
kubectl get extensionversions.kubesphere.io -l kubesphere.io/extension-ref=openkruise
kubectl get extensionversion openkruise-1.0.3 -o yaml
Discover deployed runtime image or controller version
kubectl get pods -n kruise-system -o wide
kubectl get deploy -n kruise-system kruise-manager -o jsonpath='{.spec.template.spec.containers[*].image}'
kubectl describe pod -n kruise-system <kruise-manager-pod>
export KS_HOST="http://<kubesphere-host>" # KubeSphere console URL (required)
export KS_USERNAME="admin" # Username (default: admin)What does the kubesphere-openkruise skill do?
KubeSphere OpenKruise management Skill. Use when user asks to install or enable OpenKruise, check OpenKruise status, view kruise pods/logs/CRDs, create or update SidecarSet, manage sidecar injection, create or update CloneSet, perform in-place update or batch rollout, uninstall or remove OpenKruise, or troubleshoot Kruise Pod, CRD, and webhook issues in KubeSphere.
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill kubesphere-openkruise --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.