* Terraform example typo's the port number in the etcd_endpoints * Causes worker etcd-gateway to fail so Container Linux updates may not been coordinated by locksmith
matchbox

Network boot and provision Container Linux clusters on virtual or physical hardware.
Announcement: A new Matchbox Terraform Provider is available for Terraform users.
Guides
- Network Setup
- Machine Lifecycle
- Background: PXE Booting
- Tutorials (QEMU/KVM/libvirt)
matchbox
matchbox is an HTTP and gRPC service that renders signed Ignition configs, cloud-configs, network boot configs, and metadata to machines to create Container Linux clusters. Groups match machines based on labels (e.g. MAC, UUID, stage, region) and use named Profiles for provisioning. Network boot endpoints provide PXE, iPXE, and GRUB. matchbox can be deployed as a binary, as an appc container with rkt, or as a Docker container.
- matchbox Service
- Profiles
- Groups
- Config Templates
- Configuration
- HTTP API
- gRPC API
- Installation
- Installing on CoreOS / Linux distros
- Installing on Kubernetes
- Running with rkt / docker
Examples
Network boot the examples on QEMU/KVM VMs to try them on your Linux laptop.
- Multi-node Kubernetes cluster
- Multi-node rktnetes cluster (i.e. Kubernetes with rkt as the container runtime)
- Multi-node self-hosted Kubernetes cluster
- Upgrading self-hosted Kubernetes clusters
- Multi-node etcd2 or etcd3 cluster
- Network boot and/or install to disk (multi-stage installs)
Enterprise
Tectonic is the enterprise-ready Kubernetes offering from CoreOS (free for 10 nodes!). The Tectonic Installer app integrates directly with matchbox through its gRPC API to provide a rich graphical client for populating matchbox with machine configs.

