k3s-oci-cluster
flannel
Our great sponsors
k3s-oci-cluster | flannel | |
---|---|---|
6 | 13 | |
210 | 8,477 | |
- | 0.7% | |
0.0 | 8.7 | |
5 months ago | 7 days ago | |
HCL | Go | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
k3s-oci-cluster
-
K8s cluster with OCI free-tier and Raspberry Pi4 (part 1)
After you've cloned the repo, go to oci/terraform.tfvars and edit all values with the ones from your notes file. This build uses the great terraform configuration files from this repo of garutilorenzo (using version 2.2; if you have errors running all of this, you should check what changed in this repo since v2.2, or 01.02.23). You can read here if you want to customize your configuration and edit the main.tf file. This is the diagram that garutilorenzo made and how your deployment will look like (this tutorial is without Longhorn and ArgoCD, with 1 server nodes + 3 worker nodes and with ingress controller set as Traefik): *note - I've got some problems with clock of WSL2 not being synced to Windows clock. And provisioning didn't worked so if you receive clock errors too, verify your time with datecommand, if out of sync just run sudo hwclock -s or sudo ntpdate time.windows.com. Now just run terraform plan and then terraform apply. If everything was ok you should have your resources created.
- Is there a step by step guide to Oracle Free Tier setups?
-
OCI free Kubernetes cluster, new terraform module release
This new release v2.0 introduces:
-
Deploy Kubernetes (K8s) on Amazon AWS using mixed on-demand and spot instances
We use the same stack used in this repository. This stack need longhorn and nginx ingress.
-
Deploy a Kubernetes cluster for free, using k3s and Oracle always free resources.
This module will deploy a Kubernetes cluster for free, using K3s and Oracle always free resources.
-
Deploy a Kubernetes cluster for free, using K3s and Oracle always free resources
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)
flannel
-
How to create a 3-node kubernetes cluster and deploy an application on my ubuntu 22.04 minibox
$ kubectl apply -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml
-
Kubernetes Setup With WSL Control Plane and Raspberry Pi Workers
--pod-network=10.244.0.0/16: This is the default CIDR for flannel, and also avoids a conflict with my internal network if calico is used (which is the plan)
- flannel - network fabric for containers, designed for Kubernetes
-
Deploy Kubernetes (K8s) on Amazon AWS using mixed on-demand and spot instances
The installation of K8s id done by kubeadm. In this installation Containerd is used as CRI and flannel is used as CNI.
-
Fully automated Kubernetes (K8s) deployment on AWS using mixed on-demand and spot instances
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.
-
flannel error: Error registering network: operation not supported
I don't use flannel but perhaps check this old issue: https://github.com/flannel-io/flannel/issues/663
-
Can't access service from other Nodes
It is definitively not normal behaviour. Cluster-internal subnets should be reachable from any node. Not being able to do so is a typical symptom of missing or misconfigured CNI. For flannel did you check this page?
-
Container base OS vs Worker node OS compatibility issues
Ask on Github.
-
K3S Calico networking Issues
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....
What are some alternatives?
oracle-cloud-terraform-examples - Oracle cloud terraform examples, provision oracle cloud resources using terraform
calico - Cloud native networking and network security
k3s-aws-terraform-cluster - Deploy an high available K3s cluster on Amazon AWS
wireguard-windows - Download WireGuard for Windows at https://www.wireguard.com/install . This repo is a mirror only. Official repository is at https://git.zx2c4.com/wireguard-windows
longhorn - Cloud-Native distributed storage built on and for Kubernetes
containerd - An open and reliable container runtime
terraform-oci-tdf-network-security - (OCI) Oracle Cloud Infrastructure module to manage security policies
ingress-nginx - Ingress-NGINX Controller for Kubernetes
terraform-hcloud-kube-hetzner - Optimized and Maintenance-free Kubernetes on Hetzner Cloud in one command!
iac-intro-terraform-packer - Assets for the "Introduction to Infrastructure as Code with Terraform and Packer" article on Dev.to
aws-terraform-examples - AWS terraform examples, provision AWS resources using terraform modules