# Guides

> Task-focused walkthroughs for common Apoxy workflows.

The guides cover the patterns most teams hit operating Apoxy: opening tunnels into
private networks, attaching routes and custom domains, redirecting and compressing
traffic at the edge, and operating the in-cluster controller. Pick the one you need;
each guide stands alone.

## Tunnels

<LinkCards
  cards={[
    {
      ix: "A · TUNNELS",
      title: "Basic tunnels",
      sub: "Expose a local HTTP server on your Apoxy domain using a tunnel.",
      href: "/docs/guides/basic-tunnels.md",
    },
    {
      ix: "B · DOCKER",
      title: "Tunnels with Docker",
      sub: "Connect a running Docker container to the Apoxy edge using a tunnel.",
      href: "/docs/guides/tunnels-with-docker.md",
    },
    {
      ix: "C · TUNING",
      title: "Tuning tunnels",
      sub: "Adjust endpoint selection, connection pooling, and DNS behavior for tunnel clients.",
      href: "/docs/guides/tuning-tunnels.md",
    },
    {
      ix: "D · K8S",
      title: "Routing to Kubernetes services",
      sub: "Address cluster services through a tunnel and the Apoxy edge.",
      href: "/docs/guides/routing-to-kubernetes-services.md",
    },
  ]}
/>

## Routing and TLS

<LinkCards
  cards={[
    {
      ix: "E · ROUTING",
      title: "Routing traffic",
      sub: "Attach routes to the default Gateway and verify traffic flow using the Gateway API.",
      href: "/docs/guides/routing-traffic.md",
    },
    {
      ix: "F · DOMAINS",
      title: "Custom domains",
      sub: "Attach a customer-owned domain to Apoxy's default Gateway with zero-downtime TLS provisioning.",
      href: "/docs/guides/custom-domains.md",
    },
    {
      ix: "G · REDIRECT",
      title: "HTTP to HTTPS redirect",
      sub: "Redirect HTTP traffic to HTTPS using the default Gateway's listeners.",
      href: "/docs/guides/http-to-https-redirect.md",
    },
    {
      ix: "H · COMPRESSION",
      title: "Response compression",
      sub: "Compress HTTP responses with gzip, brotli, or zstd — enabled by default, customizable via HTTPRouteFilter.",
      href: "/docs/guides/response-compression.md",
    },
  ]}
/>

## Operations

<LinkCards
  cards={[
    {
      ix: "I · ROTATION",
      title: "Rotating the kube-controller certificate",
      sub: "Roll the per-cluster client certificate the Apoxy controller uses, without dropping the aggregated API.",
      href: "/docs/guides/rotating-kube-controller-cert.md",
    },
    {
      ix: "J · MCP",
      title: "Query logs with Claude Code",
      sub: "Connect Claude Code to Apoxy's MCP server to query your proxy logs with natural language.",
      href: "/docs/guides/mcp-claude-code.md",
    },
    {
      ix: "K · DEBUG",
      title: "Troubleshooting",
      sub: "Debug route attachments, tunnel connectivity, and common failure modes.",
      href: "/docs/guides/troubleshooting.md",
    },
  ]}
/>