You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2019. It is now read-only.
One approach may be to create a bunch of ingress/service pairs to handle the 'external' routes currently supported by traefik on swarm (e.g. create one for sonarr.mydomain that points to the sonar listening port on swarm directly, or point to traefik on swarm)
Because #3 works, will take the following approach:
Configure traefik on k8s to reference all existing swarm-based docker containers as external services
Point haproxy load balancer to traefik running on k8s cluster for all 443/80 traffic instead of the traefik running on swarm and stop traefik on swarm
As swarm-based docker containers are migrated to the k8s cluster, adjust the traefik ingress to reference the k8s-based container instead of the same thing running on swarm
When migrating the existing docker containers from
swarm
, want to do it in a way that results in little downtime overall.The text was updated successfully, but these errors were encountered: