Re: minimal cockpit packages for target node
by Sohin Vyacheslav
03.05.2022 08:46, Martin Pitt пишет:
Hello Martin,
> What do you mean by "target node"? A system which you connect to
remotely over
> SSH, instead of direct port 9090? That is true wrt.*not* having to
> install/enable cockpit-ws, these remote machines don't need an open
cockpit
> port. This is in fact what we recommend for production machines: Run
cockpit-ws
> on an uncritical "bastion host" or use Cockpit Client [1].
>
> However, depending on what you want to do on that remote machine, you
still may
> want to add additional "Pages" like cockpit-podman or cockpit-storaged.
>
Thank you for useful link to flatpak cockpit client!
As "target node" I meant a node which plan to add to Cockpit web
interface on main server to make possible SSH login to this node and
monitoring.
I.e. it's possible to install cockpit-ws or Cockpit flatpak Client on
"bastion host" but for me interesting what is a minimal cockpit software
need to install on remote node to make possible remote SSH to it from
main server and monitoring.
As I understood it's not enough just to add a public ssh key to file
authorized_hosts on remote node.
--
Best wishes,
Vyacheslav
2 years
minimal cockpit packages for target node
by Sohin Vyacheslav
Hello,
I installed full cockpit deb-packages suit on Ubuntu-20.04 server and as
I understand for target node it's possible to install only these 2
packages: cockpit-bridge and cockpit-system to make possible monitoring
of target node, isn't it?
Thanks in advance!
--
BW,
Sohin Vyacheslav
2 years
