@@ -18,12 +18,12 @@ Two workflows automate the deployment:
1818
1919Before running workflows, ensure:
2020
21- - [ ] ✅ Netbird account created
22- - [ ] ✅ Spoke clusters installed Netbird and registered (persistent peers)
23- - [ ] ✅ GitHub runners setup key created (ephemeral)
24- - [ ] ✅ ACLs configured (` github-runners ` → ` spoke-clusters ` , TCP port 6443)
25- - [ ] ✅ GKE cluster exists for hub deployment
26- - [ ] ✅ All GitHub Secrets configured (see [ Netbird Setup Guide] ( netbird-setup-guide.md#6-github-secrets-configuration ) )
21+ - [ ] Netbird account created
22+ - [ ] Spoke clusters installed Netbird and registered (persistent peers)
23+ - [ ] GitHub runners setup key created (ephemeral)
24+ - [ ] ACLs configured (` github-runners ` → ` spoke-clusters ` , TCP port 6443)
25+ - [ ] GKE cluster exists for hub deployment
26+ - [ ] All GitHub Secrets configured (see [ Netbird Setup Guide] ( netbird-setup-guide.md#6-github-secrets-configuration ) )
2727
2828---
2929
@@ -79,7 +79,7 @@ After successful deployment:
7979
8080** Example output** :
8181```
82- 📊 Deployment Summary:
82+ Deployment Summary:
8383{
8484 "argocd_url": "https://argocd.example.com",
8585 "principal_address": "34.123.45.67",
@@ -99,7 +99,7 @@ After successful deployment, you can verify the deployment details in the workfl
9999
100100** Example output** :
101101```
102- 📊 Deployment Summary:
102+ Deployment Summary:
103103{
104104 "argocd_url": "https://argocd.example.com",
105105 "principal_address": "34.123.45.67",
@@ -155,16 +155,16 @@ Check the **"Verify ArgoCD Spoke deployment"** step output:
155155Verifying spoke-2...
156156═══════════════════════════════════════════════════════════
1571571. Checking namespace...
158- ✅ Namespace exists
158+ Namespace exists
1591592. Checking ArgoCD pods...
160- ✅ All pods ready
160+ All pods ready
1611613. Checking agent connection...
162- ✅ Agent connected to principal
162+ Agent connected to principal
1631634. Checking certificates...
164- ✅ Client certificate exists
165- ✅ CA certificate exists
164+ Client certificate exists
165+ CA certificate exists
166166
167- ✅ All spoke clusters deployed and connected successfully!
167+ All spoke clusters deployed and connected successfully!
168168```
169169
170170---
@@ -195,10 +195,10 @@ Use `adopt_existing_resources=true` when:
195195════════════════════════════════════════════════════════════════
196196Checking for existing ArgoCD resources to import...
197197════════════════════════════════════════════════════════════════
198- ✓ Found existing argocd namespace
198+ Found existing argocd namespace
199199Importing into Terraform state...
200200Successfully imported kubernetes_namespace.hub_argocd
201- ✓ Found existing ArgoCD Helm release
201+ Found existing ArgoCD Helm release
202202════════════════════════════════════════════════════════════════
203203Import check complete! Proceeding with Terraform operations...
204204════════════════════════════════════════════════════════════════
@@ -487,10 +487,10 @@ kubectl get pods -n guestbook-helm --context spoke-2
487487** Q: How do I verify spoke clusters are successfully connected?**
488488
489489** A:** Check the workflow logs for the "Verify ArgoCD Spoke deployment" step. Look for all green checkmarks:
490- - ✅ Namespace exists
491- - ✅ All pods ready
492- - ✅ Agent connected to principal
493- - ✅ Client certificate exists
490+ - Namespace exists
491+ - All pods ready
492+ - Agent connected to principal
493+ - Client certificate exists
494494
495495Or verify manually: ` kubectl --context=spoke-2 logs -n argocd -l app.kubernetes.io/name=argocd-agent --tail=20 | grep "connected" `
496496
0 commit comments