CadolesKube/typhoon
7
0
Fork 0
mirror of https://github.com/puppetmaster/typhoon.git synced 2024-12-25 18:49:33 +01:00
Code Issues Packages Projects Releases Wiki Activity
a99a990d49
typhoon/digital-ocean/container-linux/kubernetes
History
Dalton Hubble eda78db08e Change Flatcar kubelet.service container from rkt to docker 
* Use docker to run the `kubelet.service` container
* Update Kubelet mounts to match Fedora CoreOS
* Remove unused `/etc/ssl/certs` mount (see
https://github.com/poseidon/typhoon/pull/810)
* Remove unused `/usr/share/ca-certificates` mount
* Remove `/etc/resolv.conf` mount, Docker default is ok
* Change `delete-node.service` to use docker instead of rkt
and inline ExecStart, as was done on Fedora CoreOS
* Fix permission denied on shutdown `delete-node`, caused
by the kubeconfig mount changing with the introduction of
node TLS bootstrap

Background

* podmand, rkt, and runc daemonless container process runners
provide advantages over the docker daemon for system containers.
Docker requires workarounds for use in systemd units where the
ExecStart must tail logs so systemd can monitor the daemonized
container. https://github.com/moby/moby/issues/6791
* Why switch then? On Flatcar Linux, podman isn't shipped. rkt
works, but isn't developing while container standards continue
to move forward. Typhoon has used runc for the Kubelet runner
before in Fedora Atomic, but its more low-level. So we're left
with Docker, which is less than ideal, but shipped in Flatcar
* Flatcar Linux appears to be shifting system components to
use docker, which does provide some limited guards against
breakages (e.g. Flatcar cannot enable docker live restore)
2020-10-18 23:24:45 -07:00
..
cl Change Flatcar kubelet.service container from rkt to docker 2020-10-18 23:24:45 -07:00
bootstrap.tf Remove asset_dir variable and optional asset writes 2020-10-17 15:00:15 -07:00
controllers.tf Remove references to CoreOS Container Linux 2020-09-24 20:51:02 -07:00
LICENSE Add LICENSE to top-level of each module 2017-09-28 20:41:19 -07:00
network.tf Isolate each DigitalOcean cluster in its own VPC 2020-06-28 23:25:30 -07:00
outputs.tf Remove asset_dir variable and optional asset writes 2020-10-17 15:00:15 -07:00
README.md Update Kubernetes from v1.19.2 to v1.19.3 2020-10-14 20:47:49 -07:00
ssh.tf Rename CLC files and favor Terraform list index syntax 2019-12-28 12:14:01 -08:00
variables.tf Remove asset_dir variable and optional asset writes 2020-10-17 15:00:15 -07:00
versions.tf Migrate from Terraform v0.12.x to v0.13.x 2020-08-12 01:54:32 -07:00
workers.tf Isolate each DigitalOcean cluster in its own VPC 2020-06-28 23:25:30 -07:00

README.md

Typhoon

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

  • Kubernetes v1.19.3 (upstream)
  • Single or multi-master, Calico or Cilium or flannel networking
  • On-cluster etcd with TLS, RBAC-enabled, network policy
  • Advanced features like snippets customization
  • Ready for Ingress, Prometheus, Grafana, CSI, and other addons

Docs

Please see the official docs and the Digital Ocean tutorial.