traefik

Traefik cloud-native reverse proxy. Use for container networking.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

traefik is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Traefik cloud-native reverse proxy. Use for container networking.

Teams using traefik should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/traefik/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/traefik/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/traefik/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How traefik Compares

Feature / Agent	traefik	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Traefik cloud-native reverse proxy. Use for container networking.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Traefik

Traefik is a modern reverse proxy that auto-discovers services. v3.0 (2025) supports **Wasm Plugins** and the **Kubernetes Gateway API**.

## When to Use

- **Docker/K8s**: It watches the Docker socket or K8s API and reconfigures itself automatically. No config file edits needed for new services.
- **Ease of Use**: Automatic Let's Encrypt (ACME) integration is best-in-class.
- **Middleware**: Built-in auth (Basic, ForwardAuth), rate limiting, and circuit breakers.

## Quick Start (Docker Compose)

```yaml
labels:
  - "traefik.enable=true"
  - "traefik.http.routers.my-app.rule=Host(`example.com`)"
  - "traefik.http.routers.my-app.entrypoints=websecure"
  - "traefik.http.routers.my-app.tls.certresolver=myresolver"
```

## Core Concepts

### Providers

Sources of configuration (Docker, Kubernetes, File, Consul).

### EntryPoints

Network ports (80, 443).

### Routers

Connect requests to Services based on Rules (Host, Path).

### Middleware

Modify requests (StripPrefix, Compress, Auth).

## Best Practices (2025)

**Do**:

- **Use v3 syntax**: Adhere to the structure of `routers` and `services`.
- **Use Dashboard**: The web UI is great for debugging routing issues.
- **Use Let's Encrypt**: TLS challenge handling is seamless.

**Don't**:

- **Don't expose Dashboard publicly**: It reveals infrastructure details. Secure it with middleware.

## References

- [Traefik Documentation](https://doc.traefik.io/traefik/)