Minimal and free Kubernetes distribution with Terraform
Go to file
Dalton Hubble d784b0fca6 Switch to quay.io/poseidon tagged system containers 2018-04-25 18:15:18 -07:00
.github Write documentation for Fedora Atomic 2018-04-24 01:10:27 -07:00
addons Update nginx-ingress from 0.12.0 to 0.13.0 2018-04-18 21:12:09 -07:00
aws Switch to quay.io/poseidon tagged system containers 2018-04-25 18:15:18 -07:00
bare-metal Switch to quay.io/poseidon tagged system containers 2018-04-25 18:15:18 -07:00
digital-ocean Switch to quay.io/poseidon tagged system containers 2018-04-25 18:15:18 -07:00
docs Switch to quay.io/poseidon tagged system containers 2018-04-25 18:15:18 -07:00
google-cloud Switch to quay.io/poseidon tagged system containers 2018-04-25 18:15:18 -07:00
CHANGES.md Update Calico from v3.0.4 to v3.1.1 2018-04-21 18:30:36 -07:00
CONTRIBUTING.md Fix typos in docs and CONTRIBUTING.md 2017-12-09 19:58:09 -08:00
DCO Add CONTRIBUTING.md and DCO agreement 2017-08-13 12:27:17 -07:00
LICENSE Rename project and organization 2017-08-14 19:24:04 -07:00
README.md Organize docs by operating system 2018-04-23 19:55:28 -07:00
mkdocs.yml Write documentation for Fedora Atomic 2018-04-24 01:10:27 -07:00
requirements.txt Update docs builder and material theme 2018-04-08 00:00:03 -07:00

README.md

Typhoon IRC

Typhoon is a minimal and free Kubernetes distribution.

  • Minimal, stable base Kubernetes distribution
  • Declarative infrastructure and configuration
  • Free (freedom and cost) and privacy-respecting
  • Practical for labs, datacenters, and clouds

Typhoon distributes upstream Kubernetes, architectural conventions, and cluster addons, much like a GNU/Linux distribution provides the Linux kernel and userspace components.

Features

Modules

Typhoon provides a Terraform Module for each supported operating system and platform.

Platform Operating System Terraform Module Status
AWS Container Linux aws/container-linux/kubernetes stable
AWS Fedora Atomic aws/fedora-atomic/kubernetes alpha
Bare-Metal Container Linux bare-metal/container-linux/kubernetes stable
Bare-Metal Fedora Atomic bare-metal/fedora-atomic/kubernetes alpha
Digital Ocean Container Linux digital-ocean/container-linux/kubernetes beta
Digital Ocean Fedora Atomic digital-ocean/fedora-atomic/kubernetes alpha
Google Cloud Container Linux google-cloud/container-linux/kubernetes beta
Google Cloud Fedora Atomic google-cloud/fedora-atomic/kubernetes very alpha

Documentation

Usage

Define a Kubernetes cluster by using the Terraform module for your chosen platform and operating system. Here's a minimal example:

module "google-cloud-yavin" {
  source = "git::https://github.com/poseidon/typhoon//google-cloud/container-linux/kubernetes?ref=v1.10.1"
  
  providers = {
    google   = "google.default"
    local    = "local.default"
    null     = "null.default"
    template = "template.default"
    tls      = "tls.default"
  }

  # Google Cloud
  cluster_name  = "yavin"
  region        = "us-central1"
  dns_zone      = "example.com"
  dns_zone_name = "example-zone"

  # configuration
  ssh_authorized_key = "ssh-rsa AAAAB3Nz..."
  asset_dir          = "/home/user/.secrets/clusters/yavin"
  
  # optional
  worker_count = 2
}

Fetch modules, plan the changes to be made, and apply the changes.

$ terraform init
$ terraform get --update
$ terraform plan
Plan: 37 to add, 0 to change, 0 to destroy.
$ terraform apply
Apply complete! Resources: 37 added, 0 changed, 0 destroyed.

In 4-8 minutes (varies by platform), the cluster will be ready. This Google Cloud example creates a yavin.example.com DNS record to resolve to a network load balancer across controller nodes.

$ export KUBECONFIG=/home/user/.secrets/clusters/yavin/auth/kubeconfig
$ kubectl get nodes
NAME                                          STATUS   AGE    VERSION
yavin-controller-0.c.example-com.internal     Ready    6m     v1.10.1
yavin-worker-jrbf.c.example-com.internal      Ready    5m     v1.10.1
yavin-worker-mzdm.c.example-com.internal      Ready    5m     v1.10.1

List the pods.

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                      READY  STATUS    RESTARTS  AGE
kube-system   calico-node-1cs8z                         2/2    Running   0         6m
kube-system   calico-node-d1l5b                         2/2    Running   0         6m
kube-system   calico-node-sp9ps                         2/2    Running   0         6m
kube-system   kube-apiserver-zppls                      1/1    Running   0         6m
kube-system   kube-controller-manager-3271970485-gh9kt  1/1    Running   0         6m
kube-system   kube-controller-manager-3271970485-h90v8  1/1    Running   1         6m
kube-system   kube-dns-1187388186-zj5dl                 3/3    Running   0         6m
kube-system   kube-proxy-117v6                          1/1    Running   0         6m
kube-system   kube-proxy-9886n                          1/1    Running   0         6m
kube-system   kube-proxy-njn47                          1/1    Running   0         6m
kube-system   kube-scheduler-3895335239-5x87r           1/1    Running   0         6m
kube-system   kube-scheduler-3895335239-bzrrt           1/1    Running   1         6m
kube-system   pod-checkpointer-l6lrt                    1/1    Running   0         6m

Non-Goals

Typhoon is strict about minimalism, maturity, and scope. These are not in scope:

  • In-place Kubernetes Upgrades
  • Adding every possible option
  • Openstack or Mesos platforms

Help

Ask questions on the IRC #typhoon channel on freenode.net.

Motivation

Typhoon powers the author's cloud and colocation clusters. The project has evolved through operational experience and Kubernetes changes. Typhoon is shared under a free license to allow others to use the work freely and contribute to its upkeep.

Typhoon addresses real world needs, which you may share. It is honest about limitations or areas that aren't mature yet. It avoids buzzword bingo and hype. It does not aim to be the one-solution-fits-all distro. An ecosystem of Kubernetes distributions is healthy.

Social Contract

Typhoon is not a product, trial, or free-tier. It is not run by a company, does not offer support or services, and does not accept or make any money. It is not associated with any operating system or platform vendor.

Typhoon clusters will contain only free components. Cluster components will not collect data on users without their permission.

Donations

Typhoon does not accept money donations. Instead, we encourage you to donate to one of these organizations to show your appreciation.