RepoAI
Browse MCPs

KubeSphere Gateway

94TrustedShips scripts

External traffic ingress management for KubeSphere using ingress-nginx controllers.

What it does

Kubesphere Gateway organizes how your KubeSphere environment handles external requests by deploying and maintaining ingress-nginx controllers. It introduces a structured hierarchy for traffic routing, allowing you to manage gateways at the cluster, workspace, or individual project level with consistency across your infrastructure.

The skill provides automated lifecycle support for these controllers, handling deployment and configuration through standard KubeSphere custom resources. It gives your assistant the ability to inspect the health of gateways, verify their operational status, and oversee batch version updates to ensure consistent ingress performance.

When it earns its place

Reach for it when…

Use this skill when you need to configure or troubleshoot external access points for applications running within a KubeSphere cluster. It is the appropriate choice for managing ingress-nginx lifecycle operations, checking the connectivity status of specific gateways, or deploying gateways across multi-tenant environments.

Look elsewhere when…

Do not use this for Kubernetes environments that rely exclusively on the newer Kubernetes Gateway API or alternative ingress controllers like Traefik. It does not replace core network security policies or firewall rules, nor does it assist with configuring internal service-to-service communication that does not involve the ingress-nginx layer.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • check the health status of my project gateway
  • deploy a new ingress gateway for this workspace
  • list all active gateways across my clusters
  • find out why my ingress gateway is stuck in a faulted state

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/kubesphere-gateway ~/.claude/skills/kubesphere-gateway

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/kubesphere/skills/kubesphere-gateway .claude/skills/kubesphere-gateway

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

KubeSphere Gateway changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →