Update README.md

Fix namespace changes

blueprints/01-getting-started/README.md

@@ -90,13 +90,13 @@ Once you get access to K8s API from your terminal, validate that:
 - The CloudBees Operation Center Pod is running
 
   ```sh
-  until kubectl get pod -n cloudbees-ci cjoc-0; do sleep 2 && echo "Waiting for Pod to get ready"; done; echo "OC Pod is Ready"
+  until kubectl get pod -n cbci cjoc-0; do sleep 2 && echo "Waiting for Pod to get ready"; done; echo "OC Pod is Ready"
   ```
 
 - The Ingress Controller is ready and has assigned an `ADDRESS`
 
   ```sh
-  until kubectl get ing -n cloudbees-ci cjoc; do sleep 2 && echo "Waiting for Ingress to get ready"; done; echo "Ingress Ready"
+  until kubectl get ing -n cbci cjoc; do sleep 2 && echo "Waiting for Ingress to get ready"; done; echo "Ingress Ready"
   ```
 
 - It is possible to access the CloudBees CI installation Wizard by copying the outcome of the below command in your browser:
@@ -108,7 +108,7 @@ Once you get access to K8s API from your terminal, validate that:
 Now that you’ve installed CloudBees CI and operations center, you’ll want to see your system in action. To do this, follow the steps explained in [CloudBees CI EKS Install Guide - Signing in to your CloudBees CI installation](https://docs.cloudbees.com/docs/cloudbees-ci/latest/eks-install-guide/installing-eks-using-helm#log-in).
 
   ```sh
-  kubectl exec -n cloudbees-ci -ti cjoc-0 -- cat /var/jenkins_home/secrets/initialAdminPassword
+  kubectl exec -n cbci -ti cjoc-0 -- cat /var/jenkins_home/secrets/initialAdminPassword
   ```
 
 Finally, install the suggested plugins and create the first admin user.
@@ -120,7 +120,7 @@ Finally, install the suggested plugins and create the first admin user.
 As the PVCs are not deleted by default, it is required to delete them manually as you can check on the [CloudBees CI EKS Uninstall](https://docs.cloudbees.com/docs/cloudbees-ci/latest/eks-install-guide/eks-uninstall).
 
   ```sh
-  kubectl delete --all pvc --grace-period=0 --force --namespace cloudbees-ci
+  kubectl delete --all pvc --grace-period=0 --force --namespace cbci
   ```
 
 To teardown and remove the resources created in the blueprint, the typical steps of execution are as explained in [Getting Started - Amazon EKS Blueprints for Terraform - Destroy](https://aws-ia.github.io/terraform-aws-eks-blueprints/getting-started/#destroy)