At the end of this installation, our logical architecture will look something like this.
Our installation is designed to have the Master-Node controlling the Worker Nodes. To check the product_uuid and compare, run the following command. To check the MAC address of the network interface and compare it. If these values are not unique to each node, the installation process may fail. Kubernetes uses these values to uniquely identify the nodes in the cluster. It is therefore recommended that you confirm that the Product_UUID and the MAC address are not identical in any of the nodes. Most nodes generally come with unique MAC addresses, however, in some unique cases, some Virtual Machines may have identical MAC addresses. In this tutorial, I will be using my root account. You will also need access to an account with sudo or root privileges.All your nodes should also be able to connect to one another, either on a private or public network, whichever is available.Equally, you will need to make sure that the DNF package manager is installed by default and can fetch packages remotely. We will be fetching Kubernetes and docker packages from the repository. Internet connectivity on all your nodes.This is not a strict requirement but is largely driven by the needs of the application you intend to run. It is recommended that your nodes should have at least 2 CPUs with 2GB RAM or more per machine.Three servers running CentOS 8 – 1 Master Node and 2 Worker Nodes.In a later article, we will also run through a similar installation, using podman for our containers. Podman promises to offer more flexibility when running on Kubernetes environments, but the jury remains out there.įor this article, we will run through the process of installing Kubernetes on a CentOS 8 platform, running on Docker-CE ( Community Edition). With this move, the Redhat team aims to simplify the process of creating and using containers, without needing special permissions, while at the same time, maintaining compatibility with docker images and operating them without needing a daemon.
As a matter of fact, the docker package has now been removed from the default package repository. Starting from CentOS 8 (and by extension RHEL 8), docker has now natively been replaced by podman and buildah which are tools from Redhat. These changes, mostly revolve around the installation of Docker. The process of installing a Kubernetes Cluster on CentOS 8 is almost similar to that of CentOS 7 (which you can go through here), but the process here has a few changes.
0 kommentar(er)
