Migration to Caddy #

We believe Caddy is the best way forward: it is fast and highly extensible via custom modules, where other projects either fall short or require enterprise licensing to match.

The steps to migrate from Traefik (e.g. v1.7) to Caddy are as follows:

• add labels for Caddy
• deploy a new Caddy stack
• delete your old ingress stack
• remove now outdated labels

If you are using an ingress that was previously maintained by us, please get in touch so we can remove it from our setup.

Step by step #

Our Caddy distribution is also configurable via labels. The documentation pages include example snippets for Caddy, as they did for Traefik v1.7. Our docs aim to cover common use cases; for anything else, please get in touch — we are happy to help and can support the rollout.

An important thing to note is that all labels for Caddy are prefixed with caddy., so you can add them alongside your existing labels (e.g. traefik.). They do not interfere with each other, making this transition close to zero downtime.

Once the labels are added, deploy a Caddy stack using our deployment recipe and remove or scale down your old ingress deployment. The Caddy service will eventually reconcile as the required ports (80 and 443) become available.

Once the stack is deployed, test the setup, then remove the old labels.