134
edits
Mich181189 (talk | contribs) No edit summary |
Mich181189 (talk | contribs) (Notes on the kube cluster) |
||
Line 174: | Line 174: | ||
This hosts irccat and a few other things. | This hosts irccat and a few other things. | ||
=== kube-master/kube-node/kube-node2 | === kube-master/kube-node/kube-node2 === | ||
There is a Kubernetes cluster running. People have long asked for containerisation, so here it is! | There is a Kubernetes cluster running. People have long asked for containerisation, so here it is! | ||
Line 189: | Line 189: | ||
* there's a single-node glusterfs "cluster" providing storage | * there's a single-node glusterfs "cluster" providing storage | ||
* While it's all currently on Blanton, if there was another box (or ideally two) available, it would be possible to make this much more resilient | * While it's all currently on Blanton, if there was another box (or ideally two) available, it would be possible to make this much more resilient | ||
* It's running a bleeding edge version of cert-issuer and ingress-nginx because I updated to 1.22 before things were ready :-) | |||
MetalLB is configured to allocate IP addresses in the ranges 10.0.21.128/25 and 2a00:1d40:1843:182:f000::/68 - it uses layer 2 ARP to advertise these on the LAN. | MetalLB is configured to allocate IP addresses in the ranges 10.0.21.128/25 and 2a00:1d40:1843:182:f000::/68 - it uses layer 2 ARP to advertise these on the LAN. | ||
=== gluster === | === gluster === |