Prerequisites

Prerequisites

  2 minute read  

Prerequisites

A total of at least seven machines is required:

  • one admin node
  • at least three master nodes
  • at least three worker nodes

Below are the supported operating systems with the associated minimum requirements for CPU, memory, and disk storage:

OS Minimum Requirements
Red Hat Enterprise Linux 9.6 and 9.7 8 CPU cores, 16 GB memory, 50GB disk storage
Ubuntu 24.04.02 8 CPU cores, 16 GB memory, 50GB disk storage

  • For each worker node, an additional unformatted hard disk of 50 GB is required.
    For more information about the hard disks for Rook-Ceph, visit the rook-ceph prerequisites page

  • Each machine in the cluster must be configured with the same username and password. Otherwise, the cluster creation and management process will fail.

Prerequisites for admin

The following requirements must be fulfilled on the admin machine.

  1. You need an internet connection to use the default KubeOps Registry.
registry.kubeops.net
A local registry can be used in the Airgap environment. KubeOps supports only secure registries. If you use an insecure registry, it is important to configure it accordingly in the registry configuration file (/etc/containers/registries.conf for podman, /etc/docker/deamon.json for docker)

Prerequisites for each node

The following requirements must be fulfilled on each node.

  1. You must assign a unique, lowercase hostname to every machine you use.
It is recommended to use self-explanatory hostnames.

To set the hostname on your machine, use the following command:

sudo hostnamectl set-hostname <name of node>
Example

Use the commands below to set the hostnames on each machine, for example to admin, master, node1 node2 (lowercase letters and numbers only).

sudo hostnamectl set-hostname admin
  1. Optional: To use encrypted traffic inside the cluster, follow these steps:

For RHEL machines, you need to import the ELRepo Secure Boot key into your system. You can find a detailed explanation and comprehensive instructions in our how-to guide:Importing the Secure-Boot key

This is only necessary if your system has Secure Boot enabled. If this is not the case, or if you do not want to use encryption at all, you can skip this step.