mirror of
https://github.com/outbackdingo/matchbox.git
synced 2026-01-27 10:19:35 +00:00
ba1beec39b
* Update to k8s 1.2.0 recommended admission-control settings: NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota * Improves conformance test (#71) results
Examples
These examples network boot and provision VMs into CoreOS clusters using bootcfg.
| Name | Description | CoreOS Version | FS | Docs |
|---|---|---|---|---|
| pxe | CoreOS via iPXE | alpha/1032.0.0 | RAM | reference |
| grub | CoreOS via GRUB2 Netboot | alpha/1032.0.0 | RAM | NA |
| pxe-disk | CoreOS via iPXE, with a root filesystem | alpha/1032.0.0 | Disk | reference |
| etcd, etcd-docker | iPXE boot a 3 node etcd cluster and proxy | alpha/1032.0.0 | RAM | reference |
| etcd-install | Install a 3-node etcd cluster to disk | alpha/1032.0.0 | Disk | reference |
| k8s, k8s-docker | Kubernetes cluster with 1 master and 2 workers, TLS-authentication | alpha/1032.0.0 | Disk | tutorial |
| k8s-install | Install a Kubernetes cluster to disk (1 master) | alpha/1032.0.0 | Disk | tutorial |
| bootkube | iPXE boot a self-hosted Kubernetes cluster (with bootkube) | alpha/1032.0.0 | Disk | tutorial |
| bootkube-install | Install a self-hosted Kubernetes cluster (with bootkube) | alpha/1032.0.0 | Disk | tutorial |
Tutorials
Get started running bootcfg on your Linux machine to network boot and provision clusters of VMs or physical hardware.
Experimental
These examples demonstrate booting and provisioning various (often experimental) CoreOS clusters. They have NOT been hardened for production yet. You should write or adapt Ignition configs to suit your needs and hardware.
SSH Keys
Most examples allow ssh_authorized_keys to be added for the core user as machine group metadata.
# /var/lib/bootcfg/groups/default.json
{
"name": "Example Machine Group",
"profile": "pxe",
"metadata": {
"ssh_authorized_keys": ["ssh-rsa pub-key-goes-here"]
}
}