agentleFS
kurtosis-techkurtosis-tech/kurtosis/skills/gateway/SKILL.md

gateway

Skill558 starsChanged 3 years agoApache-2.0View on GitHub

Start and manage the Kurtosis gateway for Kubernetes. The gateway forwards local ports to the Kurtosis engine and services running in a k8s cluster. Required when using Kurtosis with Kubernetes. Use when kurtosis engine status shows nothing on k8s or services aren't reachable.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not needed when using Docker backend.

    line 18
  2. Very specific:

    If this returns engine info, the gateway is working.

    line 36
  3. Distinctive:

    When services are accessed, creates additional port forwards to service pods

    line 49

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Gateway

The Kurtosis gateway creates local port forwards to the engine and services running in a Kubernetes cluster.

When you need it

The gateway is required when running Kurtosis on Kubernetes. Without it, the local CLI cannot reach the engine pod in the cluster.

Not needed when using Docker backend.

Start the gateway

# Run in the background
kurtosis gateway &

# Or in a separate terminal
kurtosis gateway

Verify it's working

kurtosis engine status

If this returns engine info, the gateway is working. If it says "No Kurtosis engine is running" but you know the engine pod is up, the gateway isn't running.

Stop the gateway

pkill -f "kurtosis gateway"

How it works

The gateway:

  1. Finds the engine pod in the kurtosis-engine-* namespace
  2. Creates a local port forward to the engine's gRPC port
  3. When services are accessed, creates additional port forwards to service pods
  4. Port mappings shown in kurtosis enclave inspect point to localhost via the gateway

Common issues

SymptomFix
No engine running but engine pod is upStart the gateway: kurtosis gateway &
Gateway crashes or disconnectsRestart: pkill -f "kurtosis gateway"; kurtosis gateway &
Port conflictsKill old gateway first: pkill -f "kurtosis gateway"
Services unreachable after gateway restartRe-inspect enclave for new port mappings

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.