For this kind of deployment, Krossboard is provided either as a ready-to-deploy OVF/VMDK virtual machine appliance, or a setup package for Ubuntu Server 18.04 LTS.
Regardless of the selected deployment approach, the installation steps described hereafter shall be achieved in a couple of minutes.
The following key points shall be considered according to the selected deployment approach:
sudoaccess) is required to perform the installation. The deployment script may have to install missing dependencies (e.g. Docker), hence the machine should have access to official/mirrored Ubuntu repositories.
Hardware requirements: Krossboard itself has a very low resources footprint, the hardware resources allocated to the instance do mainly depend on the number of Kubernetes clusters and namespaces it’ll manage. For example, assuming an environment with
10 clusterswe can start with
512 MBof memory and then refine them later according to the actual resource utilization observed on the machine.
Deploy an instance of Krossboard using the following steps, then jump to the configuration section to set up the integration with your Kubernetes clusters.
Deploy an instance of Krossboard using the following steps, then move to the configuration section to set up the integration with your Kubernetes clusters.
Go to the release page and download the latest stable setup package.
Copy the archive to the target installation machine.
tar zxf krossboard-<VERSION>.tgz cd krossboard-<VERSION>
Use this command to launch the installation.
Once the installation completed, reboot the machine to start the services.
Create (or copy via SSH) the
KUBECONFIG file of your Kubernetes clusters on the Krossboard machine.
In the next steps we consider that it’s located at
Make sure that the KUBECONFIG file is owned by the
krossboard user (a read access for the
krossboard user is also sufficient).
sudo chown krossboard:krossboard /opt/krossboard/etc/kubeconfig
Edit the Krossboard configuration file as follows.
sudo vi /opt/krossboard/etc/krossboard.env # Uncomment this line and set the KUBECONFIG variable appropriately. KUBECONFIG=/opt/krossboard/etc/kubeconfig
The configuration shall be taken into account within the next 10 minutes. However, you can force the refresh using this command.
sudo systemctl restart krossboard-data-processor-collector
Krossboard relies on Kubernetes Metrics Server to retrieve certain metrics from Kubernetes. If it’s not yet the case, the Kubernetes Metrics Server can be installed as follows on each cluster.
kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml
Open a browser tab and point it to the Krossboard URL (i.e. http:///, changing
<machine-addr> with the address of the instance).
Note: It may take a few seconds before the instance finishes its initialization, during this time you may experience a loading error in the browser.
The default username and password to sign in are:
It’s highly recommended to change this default password as soon as possible.