Currently when you try to assign a domain that’s used on another application you get an error. We are switching to a container based applications and we will be forced to first remove the domain from the original application which will create down time until the new application is fully deployed. It would be useful to deploy the container based application with the same domain and split the traffic between the two until we destroy the old application. Any change requiring to recreate the application could benefit of this.
Hello @prki ,
Load Balancing between different services is a complex topic and this is not something we support.
If you want to limit the downtime of your application you can deploy it without the domain, and when everything is running you remove the domain from your old application and attach it to the new one. This can be done using CLI to limit the duration.
Regards,
Charles-Edouard
Sure, but it will still have some downtime. We aim for zero downtime deployments and the workaround is not good enough for us.
@prki ,
If you are ready to do some work on your side, you can follow this tutorial on how to set an API Gateway: Use an API gateway in front of multiple services | Qovery
With this specific load balancing configuration for Nginx: HTTP Load Balancing | NGINX Documentation
The steps would be:
- Set up the API Gateway in front of your existing service
- Move the domain on the API Gateway
- Add your new service behind the API Gateway
- Configure your API Gateway for Round Robin
- Remove your old service.
I hope this will help you.
Charles-Edouard
This topic was automatically closed after 2 days. New replies are no longer allowed.