Merge pull request #56 from ibm-messaging/callumpjackson-patch-1

Callumpjackson patch 1

samples/AWSEKS/README.md

@@ -25,6 +25,6 @@ Navigate to *../test* directory. No modifications should be required, as the end
 
 1. Open another terminal window and run the **./getMessage.sh \<namespace\>** command. You should see all of the messages being sent by the sendMessaging command.
 
-1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **oc delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **kubectl delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the *../deploy* directory and running the command **./cleanup.sh \<namespace\>**. This will delete everything. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.

samples/AWSEKSPartnerSolution/README.md

@@ -26,6 +26,6 @@ Navigate to *../test* directory. No modifications should be required, as the end
 
 1. Open another terminal window and run the **./getMessage.sh \<namespace\>** command. You should see all of the messages being sent by the sendMessaging command.
 
-1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **oc delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **kubectl delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the *../deploy* directory and running the command **./cleanup.sh \<namespace\>**. This will delete everything. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.

samples/AzureAKS/README.md

@@ -33,7 +33,7 @@ Navigate to the *../test* directory. No modifications should be required, as the
 
 1. Open another terminal window and run the **./getMessage.sh \<namespace\>** command. You should see all of the messages being sent by the sendMessaging command.
 
-1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal window to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **oc delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal window to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **kubectl delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the *../deploy* directory and running the command **./cleanup.sh \<namespace\>**. This will delete everything from the AKS cluster, but leave the cluster itself. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.
 

samples/GoogleKubernetesEngine/README.md

@@ -101,7 +101,7 @@ Navigate to the *../test* directory. No modifications should be required, as the
 
 1. Open another terminal window and run the **./getMessage.sh \<namespace\>** command. You should see all of the messages being sent by the sendMessaging command.
 
-1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal window to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **oc delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal window to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **kubectl delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the *../deploy* directory and running the command **./cleanup.sh \<namespace\>**. This will delete everything from the GKE cluster, but leave the cluster itself. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.
 

samples/IBMKubernetesService/README.md

@@ -26,6 +26,6 @@ Navigate to *../test* directory. No modifications should be required, as the end
 
 1. Open another terminal window and run the **./getMessage.sh \<namespace\>** command. You should see all of the messages being sent by the sendMessaging command.
 
-1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **oc delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **kubectl delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the *../deploy* directory and running the command **./cleanup.sh \<namespace\>**. This will delete everything. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.

samples/Minikube/README.md

@@ -65,7 +65,7 @@ Navigate to *../test* directory. No modifications should be required, as the end
 
 3. Open another terminal window and run the ```./sendMessageMinikubeService.sh <ipaddress> <port>``` command, in the above case this would be ```./sendMessageMinikubeService.sh 127.0.0.1 53582```. You should see all of the messages being sent by the sendMessaging command.
 1. Open another terminal window and run the ```./getMessageMinikubeService.sh <ipaddress> <port>``` command, in the above case this would be ```./getMessageMinikubeService.sh 127.0.0.1 53582```. You should see all of the messages being sent by the sendMessaging command.
-1. To see how the pods work together in action, run the **oc get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **oc delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **kubectl delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the *../deploy* directory and running the command **./cleanup.sh \<namespace\>**. This will delete everything. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.
 

samples/README.md

@@ -7,6 +7,7 @@ The following includes all the resources to test out the IBM MQ Helm Chart in se
    * [Azure AKS Free Tier using IBM MQ](AzureAKSFreeTier/README.md)
 * [Google Kubernetes Engine using IBM MQ Native HA](GoogleKubernetesEngine/README.md)
 * [IBM Cloud Kubernetes Service (IKS) using IBM MQ Native HA](IBMKubernetesService/README.md)
+* [Rancher RKE2 and OpenEBS using IBM MQ Native HA](RancherRKEOpenEBS/README.md)
 * [minikube on your own laptop](Minikube/README.md)
 * RedHat OpenShift using IBM MQ Native HA
    * Configured for the [IBM MQ Advanced for Developer container](OpenShiftNativeHA/README.md)

samples/RancherRKEOpenEBS/README.md

@@ -25,6 +25,6 @@ Navigate to `../test` directory. No modifications should be required, as the end
 
 1. Open another terminal window and run the `./getMessage.sh <namespace>` command. You should see all of the messages being sent by the sendMessaging command.
 
-1. To see how the pods work together in action, run the `kubectl get pod | grep secureapp` command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: `oc delete pod secureapphelm-ibm-mq-0` (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the `kubectl get pod | grep secureapp` command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: `kubectl delete pod secureapphelm-ibm-mq-0` (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the `../deploy` directory and running the command `./cleanup.sh <namespace>`. This will delete everything. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.

samples/VMwareTanzu/README.md

@@ -41,6 +41,6 @@ Navigate to *../test* directory. No modifications should be required, as the end
 
 1. Open another terminal window and run the **./getMessage.sh \<namespace\>** command. You should see all of the messages being sent by the sendMessaging command.
 
-1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **oc delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
+1. To see how the pods work together in action, run the **kubectl get pod | grep secureapp** command on another terminal windows to view the current pods, and then delete the running pod (the one with the ready state of `1/1`) by running the command: **kubectl delete pod secureapphelm-ibm-mq-0** (where the pod name is customized based on which one is active). Once the active pod is deleted, the application connections will then reconnect to the other pod.
 
 1. You can clean up the resources by navigating to the *../deploy* directory and running the command **./cleanup.sh \<namespace\>**. This will delete everything. Do not worry if you receive messages about PVCs not being found, this is a generic clean-up script and assumes a worst case scenario.