kyma 2.6 changes

jcawley5 · jcawley5 · commit 7a8d2d0a14c0 · 2022-09-28T16:43:51.000-04:00
diff --git a/tutorials/cp-kyma-api-mssql-golang/cp-kyma-api-mssql-golang.md b/tutorials/cp-kyma-api-mssql-golang/cp-kyma-api-mssql-golang.md
@@ -245,6 +245,7 @@ You can find the resource definitions in the `k8s` folder. If you performed any
 
     ```Shell/Bash
     kubectl create namespace dev
+    kubectl label namespaces dev istio-injection=enabled
     ```
     > Namespaces separate objects inside a Kubernetes cluster. Choosing a different namespace will require adjustments to the provided samples.
 
diff --git a/tutorials/cp-kyma-cap/cp-kyma-cap.md b/tutorials/cp-kyma-cap/cp-kyma-cap.md
@@ -239,6 +239,7 @@ You can find the resource definitions in the `k8s` folder. If you performed any
 
     ```Shell/Bash
     kubectl create namespace dev
+    kubectl label namespaces dev istio-injection=enabled
     ```
 
     > Namespaces separate objects inside a Kubernetes cluster. Choosing a different namespace will require adjustments to the provided samples.
diff --git a/tutorials/cp-kyma-frontend-ui5-mssql/cp-kyma-frontend-ui5-mssql.md b/tutorials/cp-kyma-frontend-ui5-mssql/cp-kyma-frontend-ui5-mssql.md
@@ -123,7 +123,9 @@ You can find the resource definitions in the `k8s` folder. If you performed any
 
     ```Shell/Bash
     kubectl create namespace dev
+    kubectl label namespaces dev istio-injection=enabled
     ```
+    
     > Namespaces separate objects inside a Kubernetes cluster. Choosing a different namespace will require adjustments to the provided samples.
 
 2. Within the project, open the `k8s/configmap.yaml` file and adjust `API_URL` by replacing `<cluster domain>` to match the Kyma runtime cluster domain:
diff --git a/tutorials/cp-kyma-mocks/add-ns.png b/tutorials/cp-kyma-mocks/add-ns.png
diff --git a/tutorials/cp-kyma-mocks/cp-kyma-mocks.md b/tutorials/cp-kyma-mocks/cp-kyma-mocks.md
@@ -36,7 +36,7 @@ The Kyma mock application contains lightweight substitutes for SAP applications
 
 [ACCORDION-BEGIN [Step 2: ](Apply resources to Kyma runtime)]
 
-1. Open the Kyma console and create the `dev` Namespace by choosing the menu option **Namespaces** and then choosing the option **Create Namespace**. Provide the name `dev`, and then choose **Create**.
+1. Open the Kyma console and create the `dev` Namespace by choosing the menu option **Namespaces** and then choosing the option **Create Namespace**. Provide the name `dev`, enable **Enable Sidecar Injection** and then choose **Create**.
 
     ![Add Namespace](add-ns.png)
 
diff --git a/tutorials/cp-kyma-mssql-deployment/cp-kyma-mssql-deployment.md b/tutorials/cp-kyma-mssql-deployment/cp-kyma-mssql-deployment.md
@@ -163,10 +163,11 @@ You can find the resource definitions in the `k8s` folder. If you performed any
 
 Run the following commands from the `database-mssql` directory using your CLI.
 
-1. Start by creating the `dev` Namespace if it doesn't already exist:
+1. Start by creating the `dev` Namespace and enabling istio if it doesn't already exist:
 
     ```Shell/Bash
     kubectl create namespace dev
+    kubectl label namespaces dev istio-injection=enabled
     ```
     > Namespaces separate objects inside a Kubernetes cluster. Choosing a different namespace will require adjustments to the provided samples.
 
