The KUBErnetes INITiator

KubeInit provides Ansible playbooks and roles for the deployment and configuration of multiple Kubernetes distributions.

KubeInit's mission is to have a fully automated way to deploy in a single command a curated list of prescribed architectures based on the following principles (G.I.V.E.).

Guide new and experienced users and contributors to deploy quickly and easily Kubernetes clusters based on a set of prescribed architectures.

Incentivate new users and contributors to overcoming the learning curve to successfully deploy complex Kubernetes scenarios.

Verify automatically that the defined prescribed architectures work seamlessly.

Engage with the upstream community for giving and receiving feedback, and cross-pollination to spark and amplify creativity, serendipity, and interdisciplinary friction.

KubeInit's documentation is hosted in this same repository.

K8s distribution: OKD

Driver: Libvirt

OS: CentOS/Fedora, Debian/Ubuntu

• A fresh deployed server with enough RAM and disk space (120GB in RAM and 300GB in disk) and CentOS 8 (it should work also in Fedora/Debian/Ubuntu hosts).
• We assume that the hypervisor node is called nyctea (defined in the inventory).
• Have root passwordless access with certificates.
• Adjust the inventory file to suit your needs i.e. the worker nodes you will need in your cluster.

The following example command will deploy a multi-master OKD 4.5 cluster with 1 worker node in a single command and in approximately 30 minutes.

git clone https://github.com/Kubeinit/kubeinit.git
cd kubeinit
ansible-playbook \
    --user root \
    -v -i ./hosts/okd/inventory \
    --become \
    --become-user root \
    ./playbooks/okd.yml

After provisioning any of the scenarios, you should have your environment ready to go. To connect to the nodes from the hypervisor use the IP addresses from the inventory files.

• The easiest and fastest way to deploy an OKD 4.5 cluster in a Libvirt/KVM Host
• KubeInit external access for OpenShift/OKD deployments with Libvirt
• KubeInit: Inheriting good practices from the OpenStack ecosystem to improve the way we deploy OKD/OpenShift