From 856eb6a915683bfd231fb6af555126c521c30d19 Mon Sep 17 00:00:00 2001
From: tehNooB <125163838+JamesTurland@users.noreply.github.com>
Date: Thu, 19 Oct 2023 16:51:15 +0100
Subject: [PATCH] Update deploy.sh

---
 Kubernetes/Traefik-Crowdsec-PiHole/deploy.sh | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/Kubernetes/Traefik-Crowdsec-PiHole/deploy.sh b/Kubernetes/Traefik-Crowdsec-PiHole/deploy.sh
index d1482c9..f014274 100644
--- a/Kubernetes/Traefik-Crowdsec-PiHole/deploy.sh
+++ b/Kubernetes/Traefik-Crowdsec-PiHole/deploy.sh
@@ -65,16 +65,16 @@ kubectl get svc -n traefik
 kubectl get pods -n traefik
 
 # Step 6: Apply Middleware
-kubectl apply -f default-headers.yaml
+kubectl apply -f ~/Helm/Traefik/default-headers.yaml
 
 # Step 7: Create Secret for Traefik Dashboard
-kubectl apply -f secret-dashboard.yaml
+kubectl apply -f ~/Helm/Traefik/Dashboard/secret-dashboard.yaml
 
-# Step 8: Apply Middleware
-kubectl apply -f middleware.yaml
+# Step 8: Apply Middleware to Dashboard
+kubectl apply -f ~/Helm/Traefik/Dashboard/middleware.yaml
 
-# Step 9: Apply Ingress to Access Service
-kubectl apply -f ingress.yaml
+# Step 9: Apply Ingress to Dashboard Service
+kubectl apply -f ~/Helm/Traefik/Dashboard/ingress.yaml
 
 # Step 10: Install Cert-Manager (should already have this with Rancher deployment)
 # Check if we already have it by querying namespace
@@ -94,10 +94,10 @@ else
 fi
 
 # Step 11: Apply secret for certificate (Cloudflare)
-kubectl apply -f secret-cf-token.yaml
+kubectl apply -f ~/Helm/Traefik/Cert-Manager/Issuers/secret-cf-token.yaml
 
 # Step 12: Apply production certificate issuer (technically you should use the staging to test as per documentation)
-kubectl apply -f letsencrypt-production.yaml
+kubectl apply -f ~/Helm/Traefik/Cert-Manager/Issuers/letsencrypt-production.yaml
 
 # Step 13: Apply production certificate
-kubectl apply -f your-domain-com.yaml
+kubectl apply -f ~/Helm/Traefik/Cert-Manager/Certificates/Production/your-domain-com.yaml