Managing Nodes

Navigation:  Administration >

Managing Nodes

Previous pageReturn to chapter overviewNext page

Log in to KuberDock as admin.


The main administrator page is Nodes page where all the nodes added to KuberDock are displayed in the list. Click on any node to get to separate node page.





In the upper area of the Node page you can view node’s status,




as well as information on node’s hardware.





Having KuberDock deployed in Amazon Web Services, it is necessary to remember that when a node is stopped and then restarted its public IP address will unavoidably be changed unless it has been assigned with an Elastic IP address. This is because of Amazon EC2 instances’ peculiarity which is beyond users’ control (refer Amazon EC2 Instance IP Addressing for details).


Click Delete to remove a node. Note that even if the node is removed from user's pod web-interface, internal and public IPs keep on working.




Use menu on the left to view logs, resource usage and other information:


General section contains information on the node and its hardware.


To view node Log files go to Logs tab. Logs are being updated automatically in real time and do not require reloading the page. All the logs that are saved via rsyslog are presented here, including:


Kernel messages log (kern.* from /dev/console);

Log level (or higher) info log (except mail and private authentication messages) (*.info;mail.none;authpriv.none;cron.none from -/var/log/messages).

Log of all the mail messages in one place. (mail.* from -/var/log/maillog).

Cron log (cron.* from -/var/log/cron).

Log of saved news errors of level crit and higher. (uucp,news.crit from -/var/log/spooler)




Note that if a node is not running, then its log is not displayed.


Monitoring section contains resource usage statistics:


CPU usage - % of CPU used;

RAM memory usage - memory used in MB;

Storage usage - number of used and available GB.