From 726dad804af962c4cdff8c0ac1ca982c12061490 Mon Sep 17 00:00:00 2001
From: martyn-v <81797311+martyn-v@users.noreply.github.com>
Date: Tue, 17 Oct 2023 00:19:52 +0000
Subject: [PATCH] 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.
---
 Kubernetes/K3S-Deploy/k3s.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Kubernetes/K3S-Deploy/k3s.sh b/Kubernetes/K3S-Deploy/k3s.sh
index ec5c8e7..6b36c01 100644
--- a/Kubernetes/K3S-Deploy/k3s.sh
+++ b/Kubernetes/K3S-Deploy/k3s.sh
@@ -139,7 +139,7 @@ sudo docker run --network host --rm ghcr.io/kube-vip/kube-vip:$KVVERSION manifes
     --leaderElection | tee $HOME/kube-vip.yaml
 
 # 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