kubesphere-gateway
KubeSphere Gateway extension management Skill (ingress-nginx based, uses Kubernetes Ingress API + Gateway CRD gateway.kubesphere.io/v2alpha2). For the newer Kubernetes Gateway API (Traefik + GatewayProxy CRD), see the kubesphere-gateway-api skill instead. Covers installation, uninstallation, status checks, gateway status inspection, and troubleshooting (gateway stuck states, Helm failures, pod issues).
npx skills add kubesphere/kubesphere --skill kubesphere-gateway --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.
# KubeSphere Gateway ## Overview Provides external access management (ingress) for KubeSphere using **ingress-nginx**. Supports three-tier gateway management: | Tier | Scope | Name Pattern | Namespace | Label | |---|---|---|---| | **Cluster** | Entire cluster | `kubesphere-router-cluster` | `kubesphere-controls-system` | `kubesphere.io/gateway-type=cluster` | | **Workspace** | Single workspace | `kubesphere-router-workspace-{workspace}` | `kubesphere-controls-system` | `kubesphere.io/gateway-type=workspace` | | **Project** | Single project/namespace | `kubesphere-router-{namespace}` | `kubesphere-controls-system` | `kubesphere.io/gateway-type=project` | Each gateway is a standalone Helm release of ingress-nginx. The gateway-controller-manager manages the lifecycle (install/upgrade/uninstall) via Helm. ### Core CRDs - **`Gateway`** (`gateway.kubesphere.io/v2alpha2`) — represents a single ingress-nginx deployment. Key fields: - `spec.appVersion` — the Helm chart version (e.g. `kubesphere-nginx-ingress-<version>`) - `spec.values` — Helm values for ingress-nginx (controller config, service type, resources, etc.) - `status.state` — `Creating`, `Updating`, `Running`, `Faulted`, `Stopped`
- Overview
- Core CRDs
- Monitoring Integration
- Before You Start
- Installation
- Step 1: Detect and Select Version
- Step 2: Detect and Select Clusters
- Step 3: Generate and Apply InstallPlan
- Status Checking
- Uninstallation
- Uninstall from all clusters
- Uninstall from specific clusters
- Gateway Operations
- List Gateways
kubectl get installplans.kubesphere.io gateway --ignore-not-found if [ -z "$LATEST_STABLE" ]; then fi echo "Available versions:" echo "$ALL_VERSIONS" echo "" echo "Latest stable: $LATEST_STABLE" echo "Ready clusters:" echo "$READY_CLUSTERS" echo "Cluster count: $CLUSTER_COUNT"
What does the kubesphere-gateway skill do?
KubeSphere Gateway extension management Skill (ingress-nginx based, uses Kubernetes Ingress API + Gateway CRD gateway.kubesphere.io/v2alpha2). For the newer Kubernetes Gateway API (Traefik + GatewayProxy CRD), see the kubesphere-gateway-api skill instead. Covers installation, uninstallation, status checks, gateway status inspection, and troubleshooting (gateway stuck states, Helm failures, pod issues).
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill kubesphere-gateway --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.
