script to create K3S_YAML secrets, updated (2)
This commit is contained in:
parent
593eb90369
commit
a196f63893
2 changed files with 4 additions and 0 deletions
|
|
@ -26,6 +26,8 @@ jobs:
|
|||
|
||||
We assume you use k3s. Otherwise, use comparable kubectl configuration.
|
||||
|
||||
Do it all in one command (experimental): `wget -q -O - https://source.c3.uber5.com/uber5-public/gha-deploy-to-k3s/raw/branch/main/encode-k3s-yaml.sh | bash`
|
||||
|
||||
- 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.
|
||||
|
|
|
|||
|
|
@ -36,3 +36,5 @@ base64 -w 0 -i k3s.yaml > k3s.yaml.b64
|
|||
echo "Base64 encoded k3s.yaml for use as K3S_YAML for deployment scripts:"
|
||||
cat k3s.yaml.b64
|
||||
|
||||
# cleanup
|
||||
rm -rf $workdir
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue