Update k3s.sh

fixes: kube-vip.yaml is created in `home`, but if the script is executed from another directory it fails to copy it to master 1.
This commit is contained in:
martyn-v 2023-10-17 00:19:52 +00:00 committed by GitHub
parent 4ad27adec1
commit 726dad804a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -139,7 +139,7 @@ sudo docker run --network host --rm ghcr.io/kube-vip/kube-vip:$KVVERSION manifes
--leaderElection | tee $HOME/kube-vip.yaml --leaderElection | tee $HOME/kube-vip.yaml
# Step 4: Copy kube-vip.yaml to master1 # Step 4: Copy kube-vip.yaml to master1
scp -i ~/.ssh/id_rsa kube-vip.yaml $user@$master1:~/kube-vip.yaml scp -i ~/.ssh/id_rsa ~/kube-vip.yaml $user@$master1:~/kube-vip.yaml
# Step 5: Connect to Master1 and move kube-vip.yaml # Step 5: Connect to Master1 and move kube-vip.yaml