k3s-oci-cluster VS flannel

We use the same stack used in this repository. This stack need longhorn and nginx ingress.

Var Required Desc region yes set the correct OCI region based on your needs availability_domain yes Set the correct availability domain. See how to find the availability domain compartment_ocid yes Set the correct compartment ocid. See how to find the compartment ocid cluster_name yes the name of your K3s cluster. Default: k3s-cluster k3s_token yes The token of your K3s cluster. How to generate a random token my_public_ip_cidr yes your public ip in cidr format (Example: 195.102.xxx.xxx/32) environment yes Current work environment (Example: staging/dev/prod). This value is used for tag all the deployed resources compute_shape no Compute shape to use. Default VM.Standard.A1.Flex. NOTE Is mandatory to use this compute shape for provision 4 always free VMs os_image_id no Image id to use. Default image: Canonical-Ubuntu-20.04-aarch64-2022.01.18-0. See how to list all available OS images oci_core_vcn_cidr no VCN CIDR. Default: oci_core_vcn_cidr oci_core_subnet_cidr10 no First subnet CIDR. Default: 10.0.0.0/24 oci_core_subnet_cidr11 no Second subnet CIDR. Default: 10.0.1.0/24 oci_identity_dynamic_group_name no Dynamic group name. This dynamic group will contains all the instances of this specific compartment. Default: Compute_Dynamic_Group oci_identity_policy_name no Policy name. This policy will allow dynamic group 'oci_identity_dynamic_group_name' to read OCI api without auth. Default: Compute_To_Oci_Api_Policy kube_api_port no Kube api default port Default: 6443 public_lb_shape no LB shape for the public LB. Default: flexible. NOTE is mandatory to use this kind of shape to provision two always free LB (public and private) http_lb_port no http port used by the public LB. Default: 80 https_lb_port no http port used by the public LB. Default: 443 k3s_server_pool_size no Number of k3s servers deployed. Default 2 k3s_worker_pool_size no Number of k3s workers deployed. Default 2 install_longhorn no Boolean value, install longhorn "Cloud native distributed block storage for Kubernetes". Default: true longhorn_release no Longhorn release. Default: v1.2.3 unique_tag_key no Unique tag name used for tagging all the deployed resources. Default: k3s-provisioner unique_tag_value no Unique value used with unique_tag_key. Default: https://github.com/garutilorenzo/k3s-oci-cluster PATH_TO_PUBLIC_KEY no Path to your public ssh key (Default: "~/.ssh/id_rsa.pub) PATH_TO_PRIVATE_KEY no Path to your private ssh key (Default: "~/.ssh/id_rsa)

The installation of K8s id done by kubeadm. In this installation Containerd is used as CRI and flannel is used as CNI.

K8s is installed through kubeadm ad uses Containerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules.

This terraform module will deploy a high available Kubernetes (K8s) cluster on Amazon AWS, using mixed on-demand and spot instances. K8s is installed through kubeadm ad usesContainerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules. Please note, this is only an example on how to Deploy a Kubernetes cluster. For a production environment you should use EKS or ECS.

I have Ubuntu 20.x and 21.x installed in my cluster, mostly because I am familiar with Ubuntu and figured the latest LTS versions would be a good idea to use for docker swarm and now kubernetes.... But there is a kernel bug, (k3s issue link and flannel issue link) with VXLAN that makes the default flannel container networking interface not work..... So I decided to Calico as the CNI to experiment with it, but I have been running to issues with BIRD is not ready: errors on only 2 of my nodes..... Which is an improvement then all of my nodes having the error like a couple of days ago.... but it is frustrating that only 2 have the error....

Flannel cni has a special requirement - it needs the k8s cluster to have a preassigned CIDR (see here). IDK how to do that in a live cluster, as I had run kubeadm reset a few times already and I saw no reason not to recreate my cluster one again. And so I did. And while I was recreating the cluster, I also had a great opportunity to specify the IP address I wanted the k8s API to be accessible through.