-
|
Current setup is... complicated to manage: I have ~10 services. Nothing mission-critical. I'd like to install K3s to slowly migrate everything there - this is only for a single server, but planning to scale to another server for fail-over later this year. If I install K3s, caddy can no longer forward traffic to other containers... domains return 404. I'm guessing this is because of all the firewall rules K3s adds. Is there a way I can install k3s on the same server to only migrate one or two services at a time and test ? I appreciate your inputs ! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Your current setup sounds pretty bespoke and perhaps somewhat fragile. In general we don't recommend trying to manage multiple container runtimes on the same host, as they can conflict with each other when it comes to managing resources and iptables rules. I'd probably stand up a second host running k3s, and migrate things over to that one at a time. Modify your caddy config to forward individual things over to k3s as they are migrated. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, thanks. That was my next step. I'll first try installing k3s in a VM and see if my initial setup will work and then move/deploy 😄 |
Beta Was this translation helpful? Give feedback.
Your current setup sounds pretty bespoke and perhaps somewhat fragile. In general we don't recommend trying to manage multiple container runtimes on the same host, as they can conflict with each other when it comes to managing resources and iptables rules.
I'd probably stand up a second host running k3s, and migrate things over to that one at a time. Modify your caddy config to forward individual things over to k3s as they are migrated.