playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / nginx-ingress-manager

nginx-ingress-manager skill

/skills/02-devops-advanced/nginx-ingress-manager

This skill helps automate nginx ingress manager tasks, generating production-ready configurations and best-practice guidance for advanced DevOps workflows.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill nginx-ingress-manager

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

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

# Nginx Ingress Manager

## Overview

This skill provides automated assistance for nginx ingress manager tasks within the DevOps Advanced domain.

## When to Use

This skill activates automatically when you:
- Mention "nginx ingress manager" in your request
- Ask about nginx ingress manager 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 nginx ingress manager
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 nginx ingress manager"
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 and guides nginx ingress manager operations for advanced DevOps workflows. I provide step-by-step configuration, validation, and production-ready manifests to manage ingress routing, TLS, and traffic policies. Use it to streamline Kubernetes ingress tasks and reduce manual errors.

How this skill works

I inspect your requested nginx ingress manager goals, current cluster state, and provided manifests to generate or adjust configurations. I produce Kubernetes Ingress, ConfigMap, and related TLS/secret templates, apply best-practice annotations, and validate outputs against common standards. I also flag potential permission, dependency, or configuration issues and suggest fixes.

When to use it

  • Deploying or updating nginx ingress resources in Kubernetes clusters
  • Configuring TLS, host routing, rewrites, or ingress annotations for nginx
  • Migrating ingress rules between environments or consolidating host rules
  • Generating production-ready manifests and validating them before apply
  • Troubleshooting routing, upstream health, or annotation conflicts

Best practices

  • Use explicit host and path rules and avoid overlapping wildcards to prevent routing conflicts
  • Keep TLS secrets and certificate management centralized (cert-manager or external CA)
  • Apply resource limits and readiness probes for ingress controller pods
  • Version control all ingress manifests and use CI validation before deployment
  • Annotate ingress for timeouts, retries, and security headers rather than embedding in app code

Example use cases

  • Create an ingress that routes example.com and app.example.com to separate services with TLS
  • Convert legacy nginx annotations to the recommended ingress class and annotation set
  • Generate a ConfigMap to tune nginx buffering, client_max_body_size, and proxies for high throughput
  • Validate and lint ingress YAML to catch missing service ports, wrong apiVersion, or malformed hosts
  • Provide step-by-step rollback instructions after a failed ingress update

FAQ

What inputs do you need to generate an ingress manifest?

Provide service names, ports, hostnames, TLS secret names, and any annotation requirements. Cluster context helps validate against live resources.

Can you help migrate annotations between nginx controller versions?

Yes. I map deprecated annotations to their current equivalents, suggest ingressClass adjustments, and produce compatible manifests.