c30862dbad
* In the k8s-install example, the k8s-certs@.service checks for the wrong file and always attempts to curl TLS assets from bootcfg. After restarts or auto-updates, if bootcfg is not running, the certs are present on disk so the kubelet and k8s cluster operate normally, while k8s-certs services fail (mostly harmless). * Fixes k8s-certs@service failures after restarts when bootcfg is unavailable. Provisioned nodes should not have a hard dependency on bootcfg service.
CoreOS on Baremetal
CoreOS on Baremetal provides guides and a service for network booting and provisioning CoreOS clusters on virtual or physical hardware.
Guides
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. UUID, MAC, 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.
- Getting Started with rkt
- Getting Started with Docker
- bootcfg Service
- Flags
- API
- Backends
- Deployment via
- Troubleshooting
- Going Further
Examples
Check the examples to find Profiles for booting and provisioning machines into higher-order CoreOS clusters. Network boot libvirt VMs to try the examples on your Linux laptop.
- Multi-node Kubernetes cluster with TLS (network booted or installed to disk)
- Multi-node etcd cluster (network booted or installed to disk)
- Multi-stage CoreOS installs
- GRUB Netboot CoreOS
- iPXE Boot CoreOS with a root fs
- iPXE Boot CoreOS