configure-ingress-networking

configure-ingress-networking is a skill for Claude Code from pjt222/agent-almanac. It costs 88 tokens per session (4,086 once invoked), scanned A, original, MIT.

A guide to exposing Kubernetes services through an Ingress, the layer that routes incoming web traffic into a cluster. It covers NGINX Ingress, automated Let's Encrypt certificates, routing, rate limits, authentication, and traffic splitting.

In plain words
What is it for?
Use it to host multiple domains or services, route by path, renew TLS certificates, apply rate limits or WAF rules, and support blue-green or canary deployments.
Why use it?
It provides one controlled public entry point for several Kubernetes services and reduces manual certificate management.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Part of the agent-almanac plugin — 122 skills, 76 agents shipped together

Good fit Use it to host multiple domains or services, route by path, renew TLS certificates, apply rate limits or WAF rules, and support blue-green or canary deployments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pjt222/agent-almanac/configure-ingress-networking
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add pjt222/agent-almanac --skill configure-ingress-networking
Clone the repo
git clone --depth 1 https://github.com/pjt222/agent-almanac

Made for: Claude Code.

Or install agent-almanac, the plugin that ships this one along with the rest of its 122 skills, 76 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for configure-ingress-networking

README.md
[![agentmods](https://agentmods.dev/badge/skills/pjt222/agent-almanac/configure-ingress-networking/github.svg)](https://agentmods.dev/skills/pjt222/agent-almanac/configure-ingress-networking)
Your own site
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/configure-ingress-networking"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/configure-ingress-networking/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for configure-ingress-networking

Your own site · 80×15
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/configure-ingress-networking"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/configure-ingress-networking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,086 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.04086
Opus 5 $0.00044 $0.02043
Sonnet 5 $0.00018 $0.00817
Haiku 4.5 $0.00009 $0.00409

Measured 9d ago against content hash fe38cc5008d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

configure-ingress-networking scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl http://$INGRESS_IP
i18n/caveman-lite/skills/configure-ingress-networking/SKILL.md · 447 lines

How it starts

The opening of the file, as written. The whole thing — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Configure Ingress Networking

Set up production-grade Kubernetes Ingress with NGINX controller, automated TLS certificates, and advanced routing capabilities.

When to Use

  • Exposing multiple Kubernetes services via single load balancer
  • Implementing path-based or host-based routing for microservices
  • Automating TLS certificate issuance and renewal with Let's Encrypt
  • Implementing rate limiting, authentication, and WAF policies
  • Setting up blue-green or canary deployments with traffic splitting
  • Configuring custom error pages and request/response modification

Inputs

  • Required: Kubernetes cluster with LoadBalancer support or MetalLB
  • Required: DNS records pointing to cluster LoadBalancer IP
  • Optional: Existing TLS certificates or Let's Encrypt account
  • Optional: OAuth2 provider for authentication
  • Optional: WAF rules (ModSecurity)
  • Optional: Prometheus for metrics collection

Procedure

See Extended Examples for complete configuration files and templates.

Step 1: Install NGINX Ingress Controller

Deploy NGINX Ingress Controller with Helm and configure cloud provider integration.

# Add NGINX Ingress Helm repository
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update

# Create namespace
kubectl create namespace ingress-nginx

# Install for cloud providers (AWS, GCP, Azure)
helm install ingress-nginx ingress-nginx/ingress-nginx \
  --namespace ingress-nginx \
  --set controller.service.type=LoadBalancer \
  --set controller.metrics.enabled=true \
  --set controller.metrics.serviceMonitor.enabled=true \
  --set controller.podAnnotations."prometheus\.io/scrape"=true \
  --set controller.podAnnotations."prometheus\.io/port"=10254

# Or install for bare-metal with NodePort
helm install ingress-nginx ingress-nginx/ingress-nginx \
  --namespace ingress-nginx \
  --set controller.service.type=NodePort \
  --set controller.service.nodePorts.http=30080 \
  --set controller.service.nodePorts.https=30443

# AWS-specific configuration with NLB
helm install ingress-nginx ingress-nginx/ingress-nginx \
  --namespace ingress-nginx \
  --set controller.service.annotations."service\.beta\.kubernetes\.io/aws-load-balancer-type"=nlb \
  --set controller.service.annotations."service\.beta\.kubernetes\.io/aws-load-balancer-backend-protocol"=tcp \
  --set controller.service.annotations."service\.beta\.kubernetes\.io/aws-load-balancer-cross-zone-load-balancing-enabled"=true

# Verify installation
kubectl get pods -n ingress-nginx
kubectl get svc -n ingress-nginx

# Wait for LoadBalancer external IP
kubectl get svc ingress-nginx-controller -n ingress-nginx -w

# Get external IP/hostname
INGRESS_IP=$(kubectl get svc ingress-nginx-controller -n ingress-nginx -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
INGRESS_HOST=$(kubectl get svc ingress-nginx-controller -n ingress-nginx -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')

echo "Ingress IP: $INGRESS_IP"
echo "Ingress Hostname: $INGRESS_HOST"

# Test controller
curl http://$INGRESS_IP
# Should return 404 (no backend configured yet)

Read the full file on GitHub · 447 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 447 lines · 88 tokens per session scan A fe38cc5008d3

Subscribe to this mod's changes

configure-ingress-networking is a skill published in the GitHub repository pjt222/agent-almanac (33 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 4,086 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.