Replies: 1 comment
-
What exactly do you mean with "Cockpit doesn't perform well if I manage 10+ servers"? Did you add them as "remote hosts" and are connected to them all the time? What exactly becomes slow/uses a lot CPU there, the cockpit-ws process (i.e. the webserver) or something else? The direct answer to your question is "yes" -- you can run several cockpit/ws container instances on different ports (you don't need a "cockpit vm" around them). But we really don't recommend staying connected to many machines all the time, that's not what Cockpit is designed to do. If your desktop/laptop runs Linux, please also consider the Cockpit Client flatpak, then you don't need a web server anywhere and can just connect to any of your servers via SSH (one at a time). |
Beta Was this translation helpful? Give feedback.
-
I have 30 ubuntu servers, and Cockpit doesn't perform well if I manage 10+ servers.
Now, my idea is to split the 30 servers to 10, 10, 10 groups and run multiple cockpit instance on the same server (obviously with different port) and manage these server groups. Please let me know if this is achievable
Reference image of what I am trying to achieve
Beta Was this translation helpful? Give feedback.
All reactions