Preparing the inventory-file

Inventory-file describes the topology of your future DEKUBE cluster

[all]
# Kubernetes Cluster
## Control-planes
### ip - kubelet ip (local Wireguard interface ip address)
master0 ansible_host=192.168.10.1 ansible_user=root ip=10.10.0.2 etcd_member_name=etcd1
master1 ansible_host=192.168.10.2 ansible_user=root ip=10.10.0.3 etcd_member_name=etcd2
master2 ansible_host=192.168.10.3 ansible_user=root ip=10.10.0.4 etcd_member_name=etcd3
 
## Worker nodes
### ip - kubelet ip (local Wireguard interface ip address)
node0 ansible_host=192.168.10.114 ansible_user=root ip=10.10.0.5
node1 ansible_host=192.168.10.181 ansible_user=root ip=10.10.0.6
node2 ansible_host=192.168.10.131 ansible_user=root ip=10.10.0.7
 
## Ingress
[kube_ingress]
ingress0 ansible_host=8.147.113.144 ansible_user=root ip=10.10.0.8
 
## VPN Server
### vpn_server_ip - VPN Server IP (always 10.10.0.1)
### vpn_server_external_ip - VPN Server IP (Public IP)
[kube_vpn]
vpn ansible_host=8.147.113.144 ansible_user=root ip=10.10.0.1 vpn_server_ip=10.10.0.1 vpn_server_external_ip=39.105.7.19 vpn_server_port=51820
 
[kube_control_plane]
master0
master1
master2
 
[etcd]
master0
master1
master2
 
[kube_vpn_clients]
node0
node1
node2
ingress0
 
[kube_node]
node0
node1
node2
ingress0
 
[dekube:children]
kube_control_plane
kube_vpn_clients
 
[k8s_cluster:children]
kube_control_plane
kube_node

Description:

• all - listing of all cluster nodes in the format specified in the example;

• kube_ingress - Ingress nodes (there can be more than one);

• kube_vpn - VPN server;

• kube_control_plane - master nodes (servers) of the cluster;

• etcd - nodes with the etcd service;

• kube_vpn_clients - worker nodes that will be connected to the VPN network;

• kube_node - nodes that will be part of the cluster;

• dekube - groups of nodes that will be included in a single VPN network (do not edit);

• k8s_cluster - groups of nodes that will be in the Kubernetes cluster (do not edit).