jpwarren/coreos-baremetal

Network boot and provision CoreOS Clusters (etcd3, Kubernetes, self-hosted Kubernetes, Torus, rktnetes, and more)

CoreOS on Baremetal

Guides and a service for network booting and provisioning CoreOS clusters on virtual or physical hardware.

Guides

• Network Setup
• Machine Lifecycle
• Background: PXE Booting

bootcfg

bootcfg is an HTTP and gRPC service that renders signed Ignition configs, cloud-configs, network boot configs, and metadata to machines to create CoreOS 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. bootcfg can be deployed as a binary, as an appc container with rkt, or as a Docker container.

• bootcfg Service
• Profiles
• Groups
• Config Templates
  • Ignition
  • Cloud-Config
• Tutorials (QEMU/KVM/libvirt)
  • bootcfg with rkt
  • bootcfg with Docker
• Configuration
• HTTP API
• gRPC API
• Installation
  • CoreOS / Linux distros
  • rkt / docker
  • Kubernetes
• Clients
  • bootcmd CLI (POC)
  • Tectonic Installer (guide, blog)
• Backends
  • FileStore
• Troubleshooting
• Going Further
  • gRPC API Usage
  • Metadata Endpoint
  • OpenPGP Signing

Examples

The examples network boot and provision CoreOS clusters. Network boot QEMU/KVM VMs to try the examples 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
• Multi-node Torus distributed storage cluster
• Network boot or Install to Disk
• Multi-stage CoreOS installs
• GRUB Netboot CoreOS
• iPXE Boot CoreOS with a root fs
• iPXE Boot CoreOS
• Lab examples