Merge pull request #425 from dmitchsplunk/main

AI POD workshop updates

Author: dmitchsplunk

content/en/ninja-workshops/14-cisco-ai-pods/10-cleanup.md

@@ -53,6 +53,15 @@ Delete the OIDC provider:
 rosa delete oidc-provider --oidc-config-id $OIDC_ID
 ```
 
+Delete the network: 
+
+> Note: add the name of the CloudFormation stack used to create the network before 
+> running the following command
+
+``` bash
+aws cloudformation delete-stack --region $AWS_REGION --stack-name <stack name i.e. rosa-network-stack-nnnnnnnnnnn>
+```
+
 Refer to [OpenShift documentation](https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws/4/html/install_clusters/rosa-hcp-deleting-cluster) 
 if you'd like to completely remove the Red Hat OpenShift Service from your AWS account. 
 

content/en/ninja-workshops/14-cisco-ai-pods/2-openshift-prereqs.md

@@ -133,11 +133,12 @@ create a new VPC in our AWS account using the following command:
 > Note:  update the region as appropriate for your environment.
 
 ``` bash
-rosa create network --param Region=us-east-2
+rosa create network network-template --param Region=us-east-2 --template-dir='.'
 ```
 
 > Important: make note of the subnet ids created as a result of this command 
-> as you'll need them when creating the cluster.
+> as you'll need them when creating the cluster.  Make a note of the CloudFormation 
+> stack name as well, which will be needed later if you want to delete the network. 
 
 > Note: by default, each AWS region is limited to 5 elastic IP addresses.  
 > If you receive the following error: 

content/en/ninja-workshops/14-cisco-ai-pods/3-deploy-openshift-cluster.md

@@ -44,7 +44,8 @@ rosa create cluster \
     --subnet-ids $SUBNET_IDS \
     --compute-machine-type $AWS_INSTANCE_TYPE \
     --replicas 2 \
-    --region $AWS_REGION 
+    --region $AWS_REGION \
+    --tags "splunkit_environment_type:non-prd,splunkit_data_classification:private"
 ```
 
 > Note that we've specified the `g5.2xlarge` instance type, which includes NVIDIA 

content/en/scenarios/debug-problems/profiling/1-build-application.md

@@ -34,19 +34,8 @@ cd workshop/profiling
 
 Now that the application is deployed, let's play with it and generate some observability data.
 
-Get the external IP address for your application instance using the following command:
-
-```` bash
-kubectl describe svc doorgame | grep "LoadBalancer Ingress"
-````
-
-The output should look like the following:
-
-```` text
-LoadBalancer Ingress:     52.23.184.60
-````
-
-You should be able to access The Door Game application by pointing your browser to port 81 of the provided IP address.  For example:
+You should be able to access The Door Game application by pointing your browser to port 81 
+of the IP address for your EC2 instance.  For example:
 
 ```` text
 http://52.23.184.60:81