mjg59 / coreos-baremetal

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

CoreOS on Baremetal

CoreOS on Baremetal provides 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, GRUB, and Pixiecore support. bootcfg can be deployed as a binary, as an appc container with rkt, or as a Docker container.

• bootcfg Service
  • Groups
  • Profiles
  • Ignition
  • Cloud-Config
• Tutorials (libvirt)
  • bootcfg with rkt
  • bootcfg with Docker
• Flags
• HTTP API
• gRPC API
• Backends
  • FileStore
• Deployment via
  • rkt
  • docker
  • Kubernetes
  • binary / systemd
• Troubleshooting
• Going Further
  • OpenPGP Signing
  • Development

Examples

The examples show how to network boot and provision higher-order CoreOS clusters. Network boot libvirt VMs to try the examples on your Linux laptop.

• Multi-node Kubernetes cluster with TLS
• Multi-node self-hosted Kubernetes cluster
• Multi-node etcd 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