playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / kubernetes-ingress-config

kubernetes-ingress-config skill

/skills/02-devops-advanced/kubernetes-ingress-config

This skill optimizes kubernetes ingress configuration by generating production ready configurations and best practice guidance for advanced devops workflows.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill kubernetes-ingress-config

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.2 KB
---
name: "kubernetes-ingress-config"
description: |
  Configure kubernetes ingress config operations. Auto-activating skill for DevOps Advanced.
  Triggers on: kubernetes ingress config, kubernetes ingress config
  Part of the DevOps Advanced skill category. Use when configuring systems or services. Trigger with phrases like "kubernetes ingress config", "kubernetes config", "kubernetes".
allowed-tools: "Read, Write, Edit, Bash(cmd:*), Grep"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Kubernetes Ingress Config

## Overview

This skill provides automated assistance for kubernetes ingress config tasks within the DevOps Advanced domain.

## When to Use

This skill activates automatically when you:
- Mention "kubernetes ingress config" in your request
- Ask about kubernetes ingress config patterns or best practices
- Need help with advanced devops skills covering kubernetes, terraform, advanced ci/cd, monitoring, and infrastructure as code.

## Instructions

1. Provides step-by-step guidance for kubernetes ingress config
2. Follows industry best practices and patterns
3. Generates production-ready code and configurations
4. Validates outputs against common standards

## Examples

**Example: Basic Usage**
Request: "Help me with kubernetes ingress config"
Result: Provides step-by-step guidance and generates appropriate configurations


## Prerequisites

- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of devops advanced concepts


## Output

- Generated configurations and code
- Best practice recommendations
- Validation results


## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |


## Resources

- Official documentation for related tools
- Best practices guides
- Community examples and tutorials

## Related Skills

Part of the **DevOps Advanced** skill category.
Tags: kubernetes, terraform, helm, monitoring, iac

Overview

This skill automates Kubernetes Ingress configuration tasks for advanced DevOps workflows. It provides step-by-step guidance, generates production-ready manifests, and validates configurations against common standards. Use it to streamline ingress patterns, enforce best practices, and produce repeatable artifacts for deployment pipelines.

How this skill works

The skill inspects your requirements (hostnames, TLS, backend services, path rules, annotations) and produces Kubernetes Ingress manifests, Helm values, or Terraform resources as requested. It applies common patterns for routing, TLS termination, path-based rules, and integration with popular ingress controllers (NGINX, Traefik, contour). Outputs include linting suggestions and validation checks to catch missing fields or incompatible annotations.

When to use it

  • Creating or updating ingress resources for new services
  • Standardizing TLS termination and certificate management
  • Migrating routing rules across clusters or controllers
  • Generating Helm or Terraform-ready ingress config
  • Validating ingress manifests before CI/CD deployment

Best practices

  • Define clear host and path rules to avoid overlapping routes
  • Use annotations sparingly and document controller-specific settings
  • Centralize TLS via cert-manager or a managed certificate service
  • Enable health checks and appropriate timeouts for backends
  • Test ingress config in a staging namespace before production rollout

Example use cases

  • Generate an NGINX ingress manifest with TLS and path-based routing for a microservice
  • Produce Helm values for ingress settings that can be templated across environments
  • Translate existing annotations to the target controller when migrating ingress controllers
  • Validate ingress manifests in CI, catching missing serviceName/servicePort or invalid hostnames
  • Create Terraform resources for ingress to include in infrastructure as code

FAQ

Which ingress controllers are supported?

I provide patterns and annotations for common controllers such as NGINX, Traefik, and Contour; customize annotations to match your controller version.

Can this generate TLS/certificate resources?

Yes. I can produce cert-manager-friendly manifests or reference managed certificates, and advise on ACME/dns01 workflows.

How do you validate generated manifests?

Validation covers required fields, hostname format, port references, and common annotation conflicts; CI-ready lint suggestions are included.