From fa5133ee889dfa2635ec967a3b072d4831241ec2 Mon Sep 17 00:00:00 2001 From: chris Date: Sun, 23 Mar 2025 20:41:41 +0000 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1359fa1..54a74e0 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ We assume you use k3s. Otherwise, use comparable kubectl configuration. - Grab k3s.yaml (\`/etc/rancher/k3s/k3s.yaml\`), copy it to /tmp/ and make it readable for you, then copy it from the master node of the k3s cluster: `scp your-node-123.uber5.com:/tmp/k3s.yaml /tmp/` - Change the `server` entry to use its public DNS name -- Insert `tls-server-name: worker1` underneath the `server` key. The value (`worker1` in this case) needs to be one of the names that are in the cert. If you get it wrong, the error message in the pipeline will tell you. +- Insert `tls-server-name: kubernetes` underneath the `server` key. The value (`kubernetes` in this case) needs to be one of the names that are in the cert. If you get it wrong, the error message in the pipeline will tell you. - encode k3s.yaml with `base64 -i /tmp/k3s.yaml -o /tmp/encoded`, and set it as the value for a secret `K3S_YAML` in gitea for the repository under "Settings > Actions > Secrets" # Open Questions