1
0
Fork 0
Commit Graph

8 Commits (master)

Author SHA1 Message Date
Dustin c7a3477c9e setup: Convert tabs to spaces 2022-07-31 01:40:16 -05:00
Dustin bd8ae87036 setup: Fix typo in README 2022-07-31 01:39:54 -05:00
Dustin 5c19643182 setup: Add virt-install commands
These are the `virt-install` commands I used to create the Control Plane
and Worker nodes in the Kubernetes cluster.
2022-07-31 00:42:37 -05:00
Dustin 66b3c83c6c setup: Fix typographical errors 2022-07-31 00:20:55 -05:00
Dustin ce077ad557 setup: Use separate kicstarts for control/worker
We're going to be using Longhorn for persistent storage.  Longhorn
allocates space on worker nodes and exposes iSCSI LUNs to other worker
nodes.  It creates sparse filesystem images under `/var/lib/longhorn`
for each volume.  Thus, we need to mount a large filesystem at that
path on each worker node for Longhorn to use.

Using two different kickstart scripts, one for the control plane nodes,
and one for the worker nodes, we can properly mount the Longhorn data
directory only on machines that will be running the Longhorn manager.

Longhorn only supports *ext4* and *XFS* filesystem types.
2022-07-31 00:14:09 -05:00
Dustin 95e563d1a9 setup: Fix ansible-playbook domain join command
* Correct example hostname
* Apply `base.yml` and `hostname.yml` separately, without
  `bootstrap.yml`, to avoid deploying *firewalld*
* Correct host IP address
2022-07-26 22:40:12 -05:00
Dustin 8b8ae3df04 setup: Use kickstart instead of Ansible
Kubernetes, or rather mostly Calico, does not play well on a machine
with an immutable root filesyste.  Specifically, Calico needs write
access to a couple of paths on the root filesystem, such as
`/etc/cni/net.d`, `/opt/cni/bin`, and
`/usr/libexec/kubernetes/kubelet-plugins/volume`.  Some of those paths
can be configured, but doing so is quite cumbersome.  While these paths
could be made writable, e.g. using symlinks or bind mounts, it would add
a lot of complexity to the *kubelet* Ansible role.  After considering
the options for a while, I decided that the best approach was probably
to mount specific filesystems at these paths.  Instead of using small
LVM logical volumes for each one, I thought it would be better to use a
single *btrfs* filesystem for all the mutable storage locations.  This
way, if I discover more paths that need to be writable, I can create
subvolumes for them, without having to try to move or resize the
existing volumes.

Now that the Kubernetes nodes need their own special kickstart file for
the disk layout, it also makes sense to handle the rest of the machine
setup there, too.  This eliminates the need for the *kubelet* Ansible
role altogether.  Any machine provisioned with this kickstart
configuration is immediately ready to become a Kubernetes control plane
or worker node.
2022-07-26 22:29:50 -05:00
Dustin f7d01f3d03 Initial commit 2022-07-25 17:52:55 -05:00