All 5 nodes are up now:

ubuntu@kenny:~$ microk8s status
microk8s is running
high-availability: yes
  datastore master nodes: 192.168.1.40:19001 192.168.1.41:19001 192.168.1.43:19001
  datastore standby nodes: 192.168.1.30:19001 192.168.1.29:19001
addons:
  enabled:
    dashboard            # The Kubernetes dashboard
    dns                  # CoreDNS
    ha-cluster           # Configure high availability on the current node
    ingress              # Ingress controller for external access
    metrics-server       # K8s Metrics Server for API access to service metrics
    storage              # Storage class; allocates storage from host directory
  disabled:
    helm                 # Helm 2 - the package manager for Kubernetes
    helm3                # Helm 3 - Kubernetes package manager
    host-access          # Allow Pods connecting to Host services smoothly
    metallb              # Loadbalancer for your Kubernetes cluster
    rbac                 # Role-Based Access Control for authorisation
    registry             # Private image registry exposed on localhost:32000
ubuntu@kenny:~$ microk8s kubectl get nodes
NAME      STATUS   ROLES    AGE     VERSION
stan      Ready    <none>   4d10h   v1.19.0-34+ff9309c628eb68
kyle      Ready    <none>   4d9h    v1.19.0-34+ff9309c628eb68
cartman   Ready    <none>   4d9h    v1.19.0-34+ff9309c628eb68
kenny     Ready    <none>   11h     v1.19.0-34+ff9309c628eb68
butters   Ready    <none>   9h      v1.19.0-34+ff9309c628eb68

One thing that seems odd is the AGE.  This seems to be the first boot, as these nodes have been powered down for some hardware assembly.  9 hours is closer to the actual age of this cycle.