> This primarily exists to take care of a fundamental issue in Docker Swarm (Kamal's orchestrator of choice) where replacing containers of a service disrupts traffic.
If that's the reason then I feel someone failed to do even the most cursory research on the topic.
I mean, a staple of any container orchestration service is the use of an ingress controller to handle dialups and blue/green deployments.
More to the point, ingress controllers is the name given to the role assigned to any of the myriad reverse proxies readily available for years, if not decades, to handle this very same usecase.
If that's the reason then I feel someone failed to do even the most cursory research on the topic.
I mean, a staple of any container orchestration service is the use of an ingress controller to handle dialups and blue/green deployments.
More to the point, ingress controllers is the name given to the role assigned to any of the myriad reverse proxies readily available for years, if not decades, to handle this very same usecase.