kubesphere-network-extension-operations
Operate the KubeSphere network extension
Install / Use
npx skills add kubesphere/kubesphere --skill kubesphere-network-extension-operationsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of kubesphere-network-extension-operations
kubesphere-network-extension-operations scores 85/100 on our quality scale, 2575th of 4,700 Development & Engineering skills we index.
Its SKILL.md is 8.9 KB long, well organised into 15 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.
With 17,059 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-06 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 86/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
kubesphere-network-extension-operations compared with similar skills
All 4 of these similar skills score higher than kubesphere-network-extension-operations; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| kubesphere-network-extension-operations (this skill)by kubesphere | 85 | 17.1k | 4mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install kubesphere-network-extension-operations?
- Run
npx skills add kubesphere/kubesphere --skill kubesphere-network-extension-operations. The install tabs above show the steps for each supported agent. - Which AI agents does kubesphere-network-extension-operations work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is kubesphere-network-extension-operations safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 86/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is kubesphere-network-extension-operations still maintained?
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: kubesphere-network-extension-operations
description: Operate the KubeSphere network extension. Use when Codex needs to install, upgrade, configure, enable, disable, or inspect the network extension; manage Calico IPPool resources, namespace bindings, migrations, or network isolation flows; or consult the bundled network extension references in this skill.
KubeSphere Network Extension Operations
Operate the network extension and its related resources with kubectl plus the bundled references in this skill. Prefer the live cluster state first, then use the copied extension references here to resolve packaging details, API shapes, and product behavior.
When to Use
- Install, upgrade, enable, disable, or inspect the
networkextension - Edit
InstallPlan.spec.configfor IPPool or NetworkPolicy feature toggles - Verify packaging details such as version, images, dependencies, or installation mode
- Manage Calico
IPPoolresources, namespace bindings, occupancy, and migration flows - Manage cluster, workspace, or project network isolation behavior
- Create, inspect, or troubleshoot Kubernetes
NetworkPolicyand namespace-level network isolation policies
Do Not Use
- Manage unrelated extensions
- Assume deprecated
network.kubesphere.ioIPPool CRDs are still the CRUD source of truth - Assume a non-Calico IPPool backend; the extension values currently support only
calico - Patch workspace, namespace, or IPPool binding metadata without reading the current live object first
Read First
Read only the references needed for the current request:
- Product behavior and upgrade caveats: references/README_zh.md
- IPPool and NetworkPolicy API flows: references/api_doc.md
- Extension defaults and feature toggles: references/values.yaml
- Packaging facts such as version, dependencies, images, and installation mode: references/extension.yaml
- Full endpoint schema details only when request or response fields matter: references/swagger.yaml
Useful rg patterns for the larger references:
rg -n "ippool|networkpol|isolate" skills/kubesphere-network-extension-operations/references/api_doc.md
rg -n "^ /(kapis|apis)/.*(ippool|networkpol)" skills/kubesphere-network-extension-operations/references/swagger.yaml
Fixed Facts
- Extension name:
network - InstallPlan name:
network - Installation mode from packaging:
Multicluster - Current packaged version in the copied reference:
1.3.0 - Supported IPPool backend in values:
global.ippool.type=calico - Main feature toggles:
global.ippool.enableglobal.ippool.webhookglobal.networkPolicy.enable
Workflow
- Read the matching bundled references for the request.
- Inspect the current live extension, InstallPlan, and relevant cluster resources.
- Apply the smallest change that satisfies the request.
- Re-read the changed resources and verify the post-change state.
Preflight Checks
kubectlmust already be configured for the target cluster.- Before any mutation, confirm the live extension state:
kubectl get extension network
kubectl get installplan network -o yaml
kubectl get extensionversion.kubesphere.io -l kubesphere.io/extension-ref=network
- Before any IPPool CRUD, confirm the Calico CRD exists:
kubectl get crd ippools.crd.projectcalico.org
- Before any network isolation mutation, inspect one live object of the same type first:
kubectl get workspace <workspace-name> -o yaml
kubectl get namespace <namespace-name> -o yaml
Extension Management
Use fixed resource names:
- extension:
network - InstallPlan:
network
When creating or updating an InstallPlan:
- Use the exact version requested by the user.
- Keep
metadata.nameandspec.extension.nameboth equal tonetwork. - Use
upgradeStrategy: Manual. - Add
clusterSchedulingonly when the user explicitly needs agent placement in member clusters. - Omit
spec.configunless the user asked for non-default settings. - On upgrade, inspect the current config first and remove or update any pinned old image tags. The bundled README warns that stale tags can block new images from being deployed.
Minimal default example:
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: network
spec:
enabled: true
extension:
name: network
version: <exact-version>
upgradeStrategy: Manual
Optional config snippet when the user asks to customize features:
config: |
global:
ippool:
enable: true
type: calico
webhook: true
networkPolicy:
enable: true
Prefer this inspection flow before install or upgrade:
kubectl get extension network -o yaml
kubectl get extensionversion network-<exact-version> -o yaml
kubectl get installplan network -o yaml
IPPool Operations
Treat Calico IPPools as the CRUD source of truth:
- Create, update, delete:
/apis/crd.projectcalico.org/v1/ippools - IP usage and occupancy details:
/kapis/network.kubesphere.io/v1alpha2/ippools/kapis/network.kubesphere.io/v1alpha2/ippools/{name}
- Migration:
POST /kapis/network.kubesphere.io/v1alpha2/ippoolmigrationsGET /kapis/network.kubesphere.io/v1alpha2/ippools/{name}/migrate
- Namespace available IPPools:
GET /kapis/network.kubesphere.io/v1alpha2/namespaces/{namespace}/ippools
Operational rules:
- Do not recreate old KubeSphere-managed IPPool CRDs from
network.kubesphere.io. - Before binding or unbinding a namespace to an IPPool, inspect a currently bound namespace and preserve the live label or annotation format already used by the cluster.
- Before migrating an IPPool, inspect the source IPPool, bound namespaces, and current pod allocations first.
- Use the examples in references/api_doc.md for bound-namespace and pod-occupancy query shapes instead of inventing new label selectors.
Suggested live inspection commands:
kubectl get ippools.crd.projectcalico.org
kubectl get ippools.crd.projectcalico.org <ippool-name> -o yaml
kubectl get namespace <namespace-name> -o yaml
kubectl get pods -A -o wide
NetworkPolicy Operations
Cluster-Scope and Namespace-Scope Kubernetes NetworkPolicy
Use Kubernetes networking.k8s.io/v1 endpoints for standard NetworkPolicy CRUD:
- List:
/kapis/networking.k8s.io/v1/networkpolicies/kapis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies
- Create:
POST /kapis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies
- Delete:
DELETE /kapis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}
Workspace and Project Isolation
The bundled API document uses inconsistent prose for the annotation key: its status-check text mentions kubesphere.io/workspace-isolate, while its patch examples use kubesphere.io/network-isolate.
Follow this rule:
- Inspect the live workspace or namespace annotations before patching.
- Unless the live cluster proves otherwise, use the example payload key
kubesphere.io/network-isolate: enabled.
Typical patch body:
{
"metadata": {
"annotations": {
"kubesphere.io/network-isolate": "enabled"
}
}
}
Namespace-Level Network Isolation Policies
Use the KubeSphere API for project-specific isolation policies:
- List:
GET /kapis/network.kubesphere.io/v1alpha1/namespaces/{namespace}/namespacenetworkpolicies
- Create:
POST /kapis/network.kubesphere.io/v1alpha1/namespaces/{namespace}/namespacenetworkpolicies
- Update:
PUT /kapis/network.kubesphere.io/v1alpha1/namespaces/{namespace}/namespacenetworkpolicies/{name}
- Delete:
DELETE /kapis/network.kubesphere.io/v1alpha1/namespaces/{namespace}/namespacenetworkpolicies/{name}
When creating or filtering these policies, preserve these labels exactly:
kubesphere.io/policy-type=egresskubesphere.io/policy-type=ingresskubesphere.io/policy-traffic=insidekubesphere.io/policy-traffic=outside
Troubleshooting
When the extension install or upgrade is stuck, gather state in this order:
kubectl describe extension network
kubectl describe installplan network
kubectl get installplan network -o jsonpath='{.status.targetNamespace}{"\n"}'
kubectl get pods,svc -n <target-namespace>
kubectl get jobs -A | rg 'helm-upgrade-network|network'
kubectl get pods -n kubesphere-system
If the InstallPlan already points to a target namespace, inspect the Helm job pod logs and any extension pods in that namespace before changing manifests again.
Rules
- Keep answers grounded in the bundled references and current live resource state.
- Prefer exact version numbers and explicit resource reads over assumptions such as "latest" or "default" without verification.
- Surface ambiguity when the copied docs and the live cluster object shape disagree.
- Treat
extension,installplan, Calico IPPools, and the live workspace or namespace objects as the source of truth.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
