kubeadm-dind-cluster - A Kubernetes multi-node test cluster based on kubeadm

•    Shell

A Kubernetes multi-node cluster for developer of Kubernetes and projects that extend Kubernetes. Based on kubeadm and DIND (Docker in Docker). Supports both local workflows and workflows utilizing powerful remote machines/cloud instances for building Kubernetes, starting test clusters and running e2e tests.

kURL - Production-grade, airgapped Kubernetes installer combining upstream k8s with overlays and popular components

•    Shell

kURL is a Kubernetes installer for airgapped and online clusters. kURL relies on kubeadm to bring up the Kubernetes control plane, but there are a variety of tasks a system administrator must perform both before and after running kubeadm init in order to have a production-ready Kubernetes cluster, such as installing Docker, configuring Pod networking, or installing kubeadm itself. The purpose of this installer is to automate those tasks so that any user can deploy a Kubernetes cluster with a single script.

kubeadm-dind-cluster - A Kubernetes multi-node test cluster based on kubeadm

•    Shell

A Kubernetes multi-node cluster for developer of Kubernetes and projects that extend Kubernetes. Based on kubeadm and DIND (Docker in Docker). Supports both local workflows and workflows utilizing powerful remote machines/cloud instances for building Kubernetes, starting test clusters and running e2e tests.

kubeadm-ha - Kubernetes high availiability deploy based on kubeadm (for v1

•    Smarty

kube-apiserver: exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. It is designed to scale horizontally – that is, it scales by deploying more instances. etcd: is used as Kubernetes’ backing store. All cluster data is stored here. Always have a backup plan for etcd’s data for your Kubernetes cluster. kube-scheduler: watches newly created pods that have no node assigned, and selects a node for them to run on. kube-controller-manager: runs controllers, which are the background threads that handle routine tasks in the cluster. Logically, each controller is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process. kubelet: is the primary node agent. It watches for pods that have been assigned to its node (either by apiserver or via local configuration file) kube-proxy: enables the Kubernetes service abstraction by maintaining network rules on the host and performing connection forwarding. keepalived cluster config a virtual IP address (192.168.20.10), this virtual IP address point to k8s-master01, k8s-master02, k8s-master03. nginx service as the load balancer of k8s-master01, k8s-master02, k8s-master03's apiserver. The other nodes kubernetes services connect the keepalived virtual ip address (192.168.20.10) and nginx exposed port (16443) to communicate with the master cluster's apiservers.

kubeadm-workshop - Showcasing a bare-metal multi-platform kubeadm setup with persistent storage and monitoring

•    Makefile

Showcasing a bare-metal multi-platform kubeadm setup with persistent storage and monitoring

kubernetes-on-arm - Kubernetes ported to ARM boards like Raspberry Pi.

•    Shell

Imagine... Your own testbed for Kubernetes with cheap Raspberry Pis and friends. This project was published in September 2015 as the first fully working way to easily set up Kubernetes on ARM devices.

kube-spawn - A tool for creating multi-node Kubernetes clusters on a Linux machine using kubeadm & systemd-nspawn

•    Go

kube-spawn is a tool for creating a multi-node Kubernetes (>= 1.8) cluster on a single Linux machine, created mostly for developers of Kubernetes but is also a Certified Kubernetes Distribution and, therefore, perfect for running and testing deployments locally. It attempts to mimic production setups by making use of OS containers to set up nodes.

kubeadm-ansible - Build a Kubernetes cluster using kubeadm via Ansible.

•    Shell

Build a Kubernetes cluster using Ansible with kubeadm. The goal is easily install a Kubernetes cluster on machines running Ubuntu 16.04, CentOS 7.

KubeNow - Deploy Kubernetes. Now!

•    HCL

Cloudflare can be optionally used to setup DNS records and SSL/TSL (HTTPS) encryption.

pharmer - 🌾 Kubernetes Cluster Manager for Kubeadm

•    Go

appscode/pre-k: Contains a set of handy commands that you run before kubeadm init.This is alpha. If you are interested to learn more, talk to us in our slack channel.

install - Contiv Installer

•    Shell

Install Contiv on your Docker Swarm or Kubernetes cluster. The Contiv Docker Swarm installer is launched from a host external to the cluster. All the nodes must be accessible to the Contiv Ansible-based installer host through SSH.

ansible-role-kubernetes - Ansible Role - Kubernetes

An Ansible Role that installs Kubernetes on Linux. Requires Docker; recommended role for Docker installation: geerlingguy.docker.

aws-kubernetes - Kubernetes cluster setup in AWS using Terraform and kubeadm

•    HCL

AWS Kubernetes is a Kubernetes cluster deployed using Kubeadm tool. It provides full integration with AWS. It is able to handle ELB load balancers, EBS disks, Route53 domains and other AWS resources. AWS Kubernetes deployes into an existing VPC / public subnet. If you don't have your VPC / subnet yet, you can use this configuration to create one. To deploy AWS Kubernetes there are no other dependencies apart from Terraform. Kubeadm is used only on the EC2 hosts and doesn't have to be installed locally.

aws-minikube - Single node Kubernetes instance implemented using Terraform and kubeadm

•    HCL

AWS Minikube is a single node Kubernetes deployment in AWS. It creates an EC2 host and deploys the Kubernetes cluster using Kubeadm tool. It provides full integration with AWS. It is also able to handle ELB load balancers, EBS disks, Route53 domains and other AWS resources. AWS Minikube deployes into an existing VPC / public subnet. If you don't have your VPC / subnet yet, you can use this configuration to create one.

terraform-aws-kubernetes - Terraform module for Kubernetes setup on AWS

•    HCL

AWS Kubernetes is a Kubernetes cluster deployed using Kubeadm tool. It provides full integration with AWS. It is able to handle ELB load balancers, EBS disks, Route53 domains etc. Although it can be run on its own, the main value is that it can be included into another Terraform configuration.

terraform-aws-minikube - Terraform module for single node Kubernetes instance bootstrapped using kubeadm

•    HCL

AWS Minikube is a single node Kubernetes deployment in AWS. It creates EC2 host and deploys Kubernetes cluster using Kubeadm tool. It provides full integration with AWS. It is able to handle ELB load balancers, EBS disks, Route53 domains etc. Although it can be run on its own, the main value is that it can be included into another Terraform configuration.

k8s-self-hosted-recovery - A short tool to recover self-hosted kubeadm provisioned kubernetes clusters

•    Shell

As of this documentation, in version 1.9 you can init a self-hosted k8s cluster, which cannot recover from reboots. This little tool solves this issue by switching to static pod plane shortly, to re-enable self-hosting again. After this, you should be able to reboot your node and expecting it to return and end up in self hosted mode.

kubeadm-bootstrap - A simple tool to generate templated, known good kubeadm configurations

•    Go

kubeadm-bootstrap is a simple tool to generate kubeadm configuration files. If you're managing lots of Kubernetes clusters, you want to make sure they are uniform, and adhere to a set of known good standards. Kubeadm is good for actually bootstrapping the Kubernetes clusters, but editing and creating the configuration files involves some degree of templating and management.

pharmer - 🌾 Kubernetes Cluster Manager for Kubeadm (Technical Preview)

•    Go

pharmer/pre-k: Contains a set of handy commands that you run before kubeadm init. Want to help improve Pharmer? Please start here.

CNI-Genie - CNI-Genie for choosing pod network of your choice during deployment time

•    Go

Without CNI-Genie, the orchestrator is bound to only a single CNI plugin. E.g., for the case of Kubernetes, without CNI-Genie, kubelet is bound to only a single CNI plugin passed to kubelet on start. CNI-Genie allows for the co-existance of multiple CNI plugins in runtime.