Best way to handle HTTP redirects within the cluster?

[rophilogene (Romaric Philogene)]

Hi @Kyle_Flavin ,

Thanks for asking. It’s a very common use case, and here is a better way to do this than updating your cluster ingresses.

You can inspire yourself from this thread:

How to deploy Windmill Enterprise via Helm Chart with Qovery

Hi @dalemccrory , good news. I’ve set up the perfect working setup with Qovery (Thanks to the Windmill team). So here is how you can leverage Windmill with Qovery. Create Postgres DB With Qovery, create a Postgres database. Inside your environment, click on New service > Create datasbase. Select Postgres, give a name and pick Managed mode if it’s for production purposes. Postgres Version 15 or latest Accessibility → Private Click on Continue and Create Deploy Windmill Helm Chart Here, we wil…

The idea is to deploy an NGINX or Caddy (recommended) container in front of your application to redirect the traffic the way you want.

The caddy configuration could be something like this:

http:// {
        bind 0.0.0.0
        reverse_proxy /other-path/* https://your-old-app.domain.tld
        reverse_proxy /* http://{$FRONTEND_HOST}:8000
}

Note: FRONTEND_APP is an environment variable that you have defined in the Qovery environment variable. {$FRONTEND_APP} is the Caddy syntax to declare an environment variable.

---

Advantages

• This is a much better and simpler way than modifying the NGINX ingress controller on your Kubernetes controller.
• There is no risk that the configuration breaks in case of a Kubernetes upgrade
• The container can be scaled the way you want - it’s stateless
• You can version (GitOps) the caddy configuration into Git