Redirecting Domains on a Traefik Ingress

I recently posted about my experience with k3s and how I’m now using it to run my blog. I also mentioned my blog’s new domain and how I’m keeping the old name working. That involved changing the Ingress resource for my blog, so I’ll show how I updated it to accept the old domains and automatically redirect to my preferred domain without needing to make WordPress itself do any redirecting.

The Ingress Controller installed by default by k3s (at least for now) is Traefik. It supports a couple of interesting features, including the ability to automatically redirect based on URL regular expressions via just two annotations. These annotations aren’t documented particularly well but I was able to figure them out through some trial and error. First, let me lay out my goals:

  • Redirect requests for these domains to my preferred domain (
  • Make the above redirection happen before WordPress is involved
  • Ensure that HTTPS still works and is forced
    • Also before WordPress itself is involved
  • This redirect should be permanent (meaning an HTTP 301)

Given the above goals, the end result really was modifying the Ingress resource in my previous post from this:

To this, which includes the required changes:

The above changes amount to three additional annotations, one to specify a permanent redirect and the other two decide what to redirect and where it is redirected. Beyond that, I needed to inform the ingress itself that it is responsible for the additional domains (the rules portion of the spec) as well as updating tls.hosts to include the additional names (so Let’s Encrypt via cert-manager can do its thing).

Of course, this required that I did the prework of pointing those domains at my server ahead of time, but this wasn’t a problem.

If the above is still called blog-ingress.yaml, save it and run:

Once things are done applying, the redirects should be all set.

Spread the love