Agent skill · DevOps & Cloud

kubesphere-gateway-api

KubeSphere Gateway API extension management Skill (Traefik based, uses Kubernetes Gateway API + GatewayProxy CRD gatewayapi.kubesphere.io/v1alpha1). This is the newer Kubernetes Gateway API standard. For the older Ingress API based gateway (ingress-nginx + Gateway CRD gateway.kubesphere.io/v2alpha2), see the kubesphere-gateway skill instead. Covers installation, uninstallation, status checks, GatewayProxy status inspection, and troubleshooting.

kubespheregithub.com/kubesphereGitHub ↗
claude-codeships scriptsNOASSERTION
Install
npx skills add kubesphere/kubesphere --skill kubesphere-gateway-api --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 15 KB
Bundled scripts: yes
Path: skills/kubesphere-gateway-api/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 17,016
Language: Go
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# KubeSphere Gateway API ## Overview Provides external access management using **Kubernetes Gateway API** with **Traefik** as the underlying proxy implementation. Supports three-tier gatewayproxy management: | Tier | Scope | Name Pattern | Namespace | Description | | ------------------- | ------------------------ | -------------------------------------- | ------------------------------ | ----------------------------- | | **Cluster** | Entire cluster | `gatewayproxy-cluster` | `kubesphere-controls-system` | Cluster-scoped GatewayProxy | | **Workspace** | Single workspace | `gatewayproxy-workspace-{workspace}` | `kubesphere-controls-system` | Workspace-scoped GatewayProxy | | **Project** | Single project/namespace | `gatewayproxy-namespace-{namespace}` | `kubesphere-controls-system` | Namespace-scoped GatewayProxy | Each **GatewayProxy** (`gatewayproxies.gatewayapi.kubesphere.io`) deploys a Traefik instance (the proxy implementation). It auto-creates a `GatewayClass`, and users can then create standard **Gateway** (`gateways.gateway.networking.k8s.io`) resources that reference that GatewayClass. The extension consists of three components: - **backend-extension** — API server on the h

What's inside
Steps it walks through
  1. Overview
  2. Key Differentiator from kubesphere-gateway
  3. Core CRDs
  4. Multi-Tenant Scoping
  5. Monitoring Integration
  6. Before You Start
  7. Installation
  8. Step 1: Detect and Select Version
  9. Step 2: Detect and Select Clusters
  10. Step 3: Generate and Apply InstallPlan
  11. Status Checking
  12. Uninstallation
  13. Uninstall from all clusters
  14. Uninstall from specific clusters
Ships with 3 files
  • scripts/check-status.sh
  • scripts/generate-installplan.sh
  • scripts/verify-uninstall.sh
Commands it runs
kubectl get installplans.kubesphere.io gateway-api --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"
More from kubesphere
All skills →
About this skill
What does the kubesphere-gateway-api skill do?

KubeSphere Gateway API extension management Skill (Traefik based, uses Kubernetes Gateway API + GatewayProxy CRD gatewayapi.kubesphere.io/v1alpha1). This is the newer Kubernetes Gateway API standard. For the older Ingress API based gateway (ingress-nginx + Gateway CRD gateway.kubesphere.io/v2alpha2), see the kubesphere-gateway skill instead. Covers installation, uninstallation, status checks, GatewayProxy status inspection, and troubleshooting.

How do I install it?

Run `npx skills add kubesphere/kubesphere --skill kubesphere-gateway-api --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.

Keep going