fix: replacing prod with baseline flow name (#40)

* replacing prod with baseline flow name

* adding extra commit

README.md

@@ -36,7 +36,7 @@ Follow these steps to explore the Kardinal Playground.
 2. 🛍️ Explore the main online boutique deployment:
 
    ```bash
-   kardinal gateway prod
+   kardinal gateway baseline
    ```
 
    This command forwards the main demo application port from within Codespaces to a URL you can access
@@ -150,7 +150,7 @@ If you encounter any issues with port forwarding or nginx, you can reset it by r
 
 ```bash
 # make sure all pods are running and 2/2
-kubectl get pods -n prod
+kubectl get pods -n baseline
 kardinal gateway <flow-id>
 ```
 
@@ -174,4 +174,5 @@ We are working with a small but selective set of initial users, join the beta [h
 
 If you run into any issues with this playground please create an issue here or email us at `[email protected]`.
 
-If you are encountering any issue with the port forwards or nginx, simply use `kardinal gateway prod` to reset the setup.
+If you are encountering any issue with the port forwards or nginx, simply use `kardinal gateway baseline` to reset the setup.
+

neon-postgres-demo/README.md

@@ -87,7 +87,7 @@ Follow these steps to explore the Kardinal Playground.
    kardinal flow create frontend kurtosistech/frontend:demo-frontend
    ```
 
-   This command sets up a development version of the frontend alongside the main version. Additionally, it will create any required dev versions of services that are downstream. In this case the frontend depends on the cartservice, that depends on the Neon DB. In order to isolate data from our prod flow, we'll need to create dev version of the cartservice and Neon DB.
+   This command sets up a development version of the frontend alongside the main version. Additionally, it will create any required dev versions of services that are downstream. In this case the frontend depends on the cartservice, that depends on the Neon DB. In order to isolate data from our baseline flow, we'll need to create dev version of the cartservice and Neon DB.
 
    The command will output a url, but it's not yet accessible because it's inside the Codespace.
 
@@ -111,10 +111,10 @@ Follow these steps to explore the Kardinal Playground.
      - Dev traffic is routed to the dev version of the frontend and through corresponding dev versions of downstream services
      - The main version still works independently in the same namespace
 
-5. 🔄 Verify prod functionality:
+5. 🔄 Verify baseline functionality:
 
    - Return to the production voting app URL (ending with -8090)
-   - Confirm that it still works and interacts with the database directly in the "prod" namespace
+   - Confirm that it still works and interacts with the database directly in the "baseline" namespace
 
 6. 🧹 Clean up the dev flow:
 

obd-demo.yaml

@@ -170,7 +170,7 @@ metadata:
   name: frontend-external
   annotations:
     kardinal.dev.service/ingress: "true"
-    kardinal.dev.service/host: "prod.app.localhost"
+    kardinal.dev.service/host: "baseline.app.localhost"
 spec:
   type: LoadBalancer
   selector: