From bd6050ea3e6854db02778f89ba18ae38002c22cb Mon Sep 17 00:00:00 2001 From: Dessa Simpson Date: Thu, 26 Oct 2023 18:37:08 +0000 Subject: [PATCH] Update 'README.md' --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 51858fe..ccc3a78 100644 --- a/README.md +++ b/README.md @@ -10,4 +10,11 @@ To run the container, use the following command adapted to your needs: ## Kubernetes To run in Kubernetes, first you need to build the docker image and push it to a registry your cluster has access to. -Once you've done that, edit k8s/deployment.yaml +Once you've done that, run `./bootstrap-k8s.sh `. `tag` should be a ref to the docker image, uploaded to a registry the cluster can access. `disk_filename` should be an xz-compressed PDP-11 disk image, which will be extracted and attached to the pdp as rq0. + +To expose the services on an external IP, first install MetalLB, and then use `./configure-metallb.sh `. `ip` should be an IP address on a broadcast domain the k8s nodes are on. + +### k3s +To use an external IP, MetalLB is required. Therefore, the cluster must not have ServiceLB enabled, as it will conflict. For k3s, just add `--disable=servicelb` to the server command line options. For k3d, create the cluster as follows: + + k3d cluster create pdp --k3s-arg "--disable=servicelb@server:*" \ No newline at end of file