From deb324cadcb1a75ffbf59635477b3387c965d829 Mon Sep 17 00:00:00 2001 From: VajiraPrabuddhaka Date: Sun, 31 Aug 2025 12:35:03 +0530 Subject: [PATCH 1/2] Update Backstage demo service name references in installation guides Fixed kubectl commands to use correct service name 'backstage-demo' instead of 'openchoreo-backstage-demo' in both single-cluster and multi-cluster installation guides. --- docs/getting-started/multi-cluster.mdx | 8 ++++---- docs/getting-started/single-cluster.mdx | 8 ++++---- .../version-v0.3.x/getting-started/multi-cluster.mdx | 8 ++++---- .../version-v0.3.x/getting-started/single-cluster.mdx | 8 ++++---- 4 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/getting-started/multi-cluster.mdx b/docs/getting-started/multi-cluster.mdx index e9eaea1..c4feaeb 100644 --- a/docs/getting-started/multi-cluster.mdx +++ b/docs/getting-started/multi-cluster.mdx @@ -359,21 +359,21 @@ Verify the installation: kubectl get pods -l app.kubernetes.io/name=backstage -n openchoreo-control-plane --context kind-openchoreo-cp # Check service -kubectl get svc openchoreo-backstage-demo -n openchoreo-control-plane --context kind-openchoreo-cp +kubectl get svc backstage-demo -n openchoreo-control-plane --context kind-openchoreo-cp ``` To access the Backstage portal: ```bash # Port forward the Backstage service in background and open browser -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 # Or if you prefer to manually open the browser: -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*openchoreo-backstage-demo.*7007:7007" +pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: diff --git a/docs/getting-started/single-cluster.mdx b/docs/getting-started/single-cluster.mdx index 2bf790b..712de82 100644 --- a/docs/getting-started/single-cluster.mdx +++ b/docs/getting-started/single-cluster.mdx @@ -303,21 +303,21 @@ Verify the installation: kubectl get pods -l app.kubernetes.io/name=backstage -n openchoreo-control-plane # Check service -kubectl get svc openchoreo-backstage-demo -n openchoreo-control-plane +kubectl get svc backstage-demo -n openchoreo-control-plane ``` To access the Backstage portal: ```bash # Port forward the Backstage service in background and open browser -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 # Or if you prefer to manually open the browser: -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*openchoreo-backstage-demo.*7007:7007" +pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: diff --git a/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx b/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx index e9eaea1..c4feaeb 100644 --- a/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx +++ b/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx @@ -359,21 +359,21 @@ Verify the installation: kubectl get pods -l app.kubernetes.io/name=backstage -n openchoreo-control-plane --context kind-openchoreo-cp # Check service -kubectl get svc openchoreo-backstage-demo -n openchoreo-control-plane --context kind-openchoreo-cp +kubectl get svc backstage-demo -n openchoreo-control-plane --context kind-openchoreo-cp ``` To access the Backstage portal: ```bash # Port forward the Backstage service in background and open browser -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 # Or if you prefer to manually open the browser: -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 --context kind-openchoreo-cp > /dev/null 2>&1 & sleep 2 # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*openchoreo-backstage-demo.*7007:7007" +pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: diff --git a/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx b/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx index 2bf790b..712de82 100644 --- a/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx +++ b/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx @@ -303,21 +303,21 @@ Verify the installation: kubectl get pods -l app.kubernetes.io/name=backstage -n openchoreo-control-plane # Check service -kubectl get svc openchoreo-backstage-demo -n openchoreo-control-plane +kubectl get svc backstage-demo -n openchoreo-control-plane ``` To access the Backstage portal: ```bash # Port forward the Backstage service in background and open browser -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 && open http://localhost:7007 # Or if you prefer to manually open the browser: -kubectl port-forward -n openchoreo-control-plane svc/openchoreo-backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 +kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 > /dev/null 2>&1 & sleep 2 # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*openchoreo-backstage-demo.*7007:7007" +pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: From 839c51c18a70b1b3a1df1c78e90bcf5b40b78aad Mon Sep 17 00:00:00 2001 From: VajiraPrabuddhaka Date: Sun, 31 Aug 2025 15:32:33 +0530 Subject: [PATCH 2/2] Fix pkill command for kubectl port-forward process termination --- docs/getting-started/multi-cluster.mdx | 2 +- docs/getting-started/single-cluster.mdx | 2 +- versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx | 2 +- .../version-v0.3.x/getting-started/single-cluster.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/getting-started/multi-cluster.mdx b/docs/getting-started/multi-cluster.mdx index c4feaeb..878c29e 100644 --- a/docs/getting-started/multi-cluster.mdx +++ b/docs/getting-started/multi-cluster.mdx @@ -373,7 +373,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 -- # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" +pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: diff --git a/docs/getting-started/single-cluster.mdx b/docs/getting-started/single-cluster.mdx index 712de82..bc843d2 100644 --- a/docs/getting-started/single-cluster.mdx +++ b/docs/getting-started/single-cluster.mdx @@ -317,7 +317,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 > # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" +pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: diff --git a/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx b/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx index c4feaeb..878c29e 100644 --- a/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx +++ b/versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx @@ -373,7 +373,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 -- # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" +pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: diff --git a/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx b/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx index 712de82..bc843d2 100644 --- a/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx +++ b/versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx @@ -317,7 +317,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 > # Then access in browser at http://localhost:7007 # To stop the port-forward when done: -pkill -f "kubectl port-forward.*backstage-demo.*7007:7007" +pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007" ``` You can verify the portal is working correctly with curl: