WebRTC/Current/WebRTCPEGuide/Deploy - Revision history

WikiSysop at 08:02, March 28, 2023

2023-03-28T08:02:10Z

Lakshmi.Krishnamurthy.IX: Published

2021-12-22T17:31:06Z

Published

Lakshmi.krishnamurthy@genesys.com: Published

2021-08-02T11:38:50Z

Published

Lakshmi.krishnamurthy@genesys.com: Published

2021-06-30T17:39:52Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Deploy WebRTC
|Context=Learn how to deploy WebRTC.
|ComingSoon=No
|Section={{Section
|alignment=Vertical
|structuredtext={{NoteFormat|Make sure to review {{Link-SomewhereInThisVersion|topic=Planning}} for the full list of prerequisites required to deploy WebRTC.|}}WebRTC uses blue-green model of deployment. It has the following main deployment principles:

*Both components - WebRTC Gateway and CoTurn Server - are deployed for each color and switched together
*Blue WebRTC Gateway is always configured to work with Blue CoTurn and green WebRTC Gateway is always configured to work with green CoTurn
*WebRTC have two FQDNs to reach active and inactive deployments:
**'''webrtc.domain.com''' - active deployment. For example: webrtc.genesyshtcc.com
**'''webrtc-test.domain.com''' - inactive deployment for tests. For example: webrtc-test.genesyshtcc.com

You can deploy WebRTC using:

*Internal CoTurn Load Balancer or
*External CoTurn Load Balancer

===Deploying WebRTC using internal CoTurn Load Balancer===
Initial deployment and Upgrade use the same sequence:

#Deploy/upgrade inactive color of deployment
#Make the cutover

You need to deploy the Color Infra package with CoTurn Load Balancer to get the IP address assigned automatically for the CoTurn Load Balancer by the infrastructure. Then, the infrastructure team should assign the IP to the CoTurn Load Balancer, create the FQDN for the IP and ensure that the IP is set in the firewall and is available from outside the cluster.
{{NoteFormat|The IP address assigned to the CoTurn Load Balancer must be external and available outside the cluster. Else, the media will not get through the WebRTC.|}}
The following image shows the steps involved in deploying WebRTC using the internal CoTurn Load Balancer:

[[File:WebRTC-Internal-Deployment.png]]

Follow the below steps to deploy WebRTC using internal CoTurn Load Balancer:

#'''Create common infrastructure elements such as dashboards and alarms''': This step deploys dashboards, alarms, and other common infrastructure elements.
#:{{NoteFormat|You should perform this step even if you do not require the dashboard and alarms.}}
#:Run the following command to create the common infrastructure elements:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=infra --set-string deployment.color="" webrtc-infra {HelmRepoPath}/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=infra --set-string deployment.color="" webrtc-infra wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Create infrastructure elements for the deployment color''': This step deploys the infrastructure objects such as Turn Load Balancer, Gateway Service Object, Gateway Network Policies, and Turn Network Policies for the given color of deployment.
#:You should also specify the INACTIVE color of deployment in this step.
#:{{NoteFormat|You should configure the <tt>deployment.coturnDeployment</tt> option with the value <tt>internal</tt> in your values.yaml file.}}
#:Run the following command to deploy the infrastructure objects:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=infra --set-string deployment.color={INACTIVE_COLOR} webrtc-infra-{INACTIVE_COLOR} {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=infra --set-string deployment.color=blue webrtc-infra-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Get the IPs from the CoTurn Load Balancers, create DNS records and firewall rules''': This step gets the IP address from the Colurn Load Balancer created in Step 2. The name of LoadBalancer will be similar to: <nowiki>webrtc-coturn-service-{COLOR}</nowiki>.
#:Create appropriate FQDN for this IP address in your DNS. This FQDN will be used by the WebRTC agents from outside the cluster to establish the RTP stream. Though you can use the IP address as it is, it is not the best practice to do so.
#'''Create CoTurn elements for the deployment color''': This step is to Upgrade/Deploy CoTurn for INACTIVE color.
#:Run the following command to upgrade/deploy the INACTIVE color of deployment:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=coturn --set-string deployment.color={INACTIVE_COLOR} webrtc-coturn-{INACTIVE_COLOR} {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=coturn --set-string deployment.color=blue webrtc-coturn-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Create Gateway elements for deployment color using the information from Step 3''': This step is to Upgrade/Deploy Gateway for INACTIVE color. You shoud also specify the extenal FQDN of the CoTurn LoadBalancer in this step using the <tt>gateway.turnExternalUriBlue</tt> or <tt>gateway.turnExternalUriGreen</tt> options.
#:Run the following command:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=gateway --set-string deployment.color={INACTIVE_COLOR} --set-string gateway.turnExternalUri{INACTIVE_COLOR}={COTURN FQDN INACTIVE_COLOR} webrtc-gateway-{INACTIVE_COLOR} {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example for Blue deployment:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml--set-string deployment.type=gateway --set-string deployment.color=blue --set-string gateway.turnExternalUriBlue=turn-blue.ext.mydoamin.com webrtc-gateway-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#:Or, you can specify the IP of the Blue CoTurn Load Balancer
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml--set-string deployment.type=gateway --set-string deployment.color=blue --set-string gateway.turnExternalUriBlue=12.106.34.55 webrtc-gateway-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Create/update Ingress controller rules for Active/Inactive routing for Gateway deployments''': This step is to Install/upgrade ingress without changing the active color. The same step is used for the Cutover.
#:{{NoteFormat|If you are deploying/upgrading <tt>green</tt>, specify the current ACTIVE color of deployment in the <tt>deployment.color</tt> option. Then specify <tt>blue</tt> and vice versa. If you deploying/upgrading <tt>green</tt> and specify <tt>green</tt> for the '''cutover''' step, the current active deployment will be switched to the just deployed/upgraded <tt>green</tt>.}}
#:You must perform this step even if you are not planning to make the cutover right now. This step is to upgrade the ingress and environment.
#:Run the following command to create/upgrade Ingress controller rules:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=cutover --set-string deployment.color={ACTIVE_COLOR} webrtc-ingress {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=cutover --set-string deployment.color=green webrtc-ingress wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>

===Deployment with external CoTurn Load Balancer===
Initial deployment and Upgrade use the same sequence:

#Deploy/upgrade inactive color of deployment
#Make the cutover

The following image shows the steps involved in deploying WebRTC using the external CoTurn Load Balancer:

[[File:WebRTC-External-Deployment-1.png]]

Follow the below steps to deploy WebRTC with external CoTurn Load Balancer

#'''Create static IPs for CoTurn''': This step is to specify the pre-created public IP for CoTurn Green in the <tt>coturn.lbIpGreen</tt> option and public IP for CoTurn Blue in the <tt>coturn.lbIpBlue</tt> option.
#'''Create DNS records for the created IPs''': This step is to specify the public FQDNs for CoTurn. Specify the pre-created public FQDN for CoTurn Green in the <tt>gateway.turnExternalUriGreen</tt> option and public FQDN for CoTurn Blue in the <tt>gateway.turnExternalUriBlu</tt>e option.
#'''Create common infrastructure elements''': This step will deploy Persistent Volumes, Persistent Volume Claims, dashboards, alarms, and other common infrastructure elements.
#:{{NoteFormat|You need to run this step even if you are not using the dashboard and alarms.}}
#:Run the following command to create the infrastructure elements:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=infra --set-string deployment.color="" webrtc-infra {HelmRepoPath}/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=infra --set-string deployment.color="" webrtc-infra wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Create infrastructure elements for deployment color''': This step is to deploy the infrastructure objects such as Turn Load Balancer, Gateway Service Object, Gateway Network Policies, and Turn Network Policies for the given color of deployment.
#:You must specify INACTIVE color of deployment for this step.
#:{{NoteFormat|Configure the <tt>deployment.coturnDeployment</tt> option with the value <tt>external</tt> in your <tt>values.yaml</tt> file.}}
#:Run the following command to create the infrastructure elements:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=infra --set-string deployment.color={INACTIVE_COLOR} webrtc-infra-{INACTIVE_COLOR} {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=infra --set-string deployment.color=blue webrtc-infra-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Create CoTurn elements for deployment color''': This step is to upgrade/deploy CoTurn for inactive color.
#:Run the following command to specify the INACTIVE color of deployment:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=coturn --set-string deployment.color={INACTIVE_COLOR} webrtc-coturn-{INACTIVE_COLOR} {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=coturn --set-string deployment.color=blue webrtc-coturn-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Create Gateway elements for deployment color''': This step is to upgrade/deploy the Gateway for inactive color.
#:{{NoteFormat|CoTurn DNS name is used for Gateway deployment as a parameter in the corresponding <tt>values.yaml</tt> file.}}
#:Run the following command to specify the INACTIVE color of deployment:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=gateway --set-string deployment.color={INACTIVE_COLOR} webrtc-gateway-{INACTIVE_COLOR} {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml--set-string deployment.type=gateway --set-string deployment.color=blue webrtc-gateway-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
#'''Create/update Ingress controller rules for Active/Inactive routing for the Gateway deployments''': This step is to install/upgrade ingress without changing the active color. The sampe step is also used for the Cutover.
#:{{NoteFormat|If you are deploying/upgrading <tt>green</tt>, specify the current ACTIVE color of deployment in the <tt>deployment.color</tt> option which is <tt>blue</tt> and vice versa. If you deploying/upgrading <tt>green</tt> and specify <tt>green</tt> for the '''cutover''' step, the current active deployment will be switched to the just deployed/upgraded <tt>green</tt>.}}
#:{{NoteFormat|You must perform this step even if you do not plan to make cutover right now. This step is to upgrade the ingress and environment.}}
#:Run the following command to create/upgrade Ingress controller rules:
#:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=cutover --set-string deployment.color={ACTIVE_COLOR} webrtc-ingress {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
#:Example:
#:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=cutover --set-string deployment.color=green webrtc-ingress wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>

===Cutover===
During cutover, it switches active color of deployment. This step should be performed only after you confirm that the newly installed/upgraded deployment is alive and functional.
You must specify the current INACTIVE color of deployment in the <tt>deployment.color</tt> option - deployment that was just deployed/upgraded and tested.
Run the following command to specify the cutover:
<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=cutover --set-string deployment.color={INACTIVE_COLOR} webrtc-ingress {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
Example:
<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=cutover --set-string deployment.color=blue webrtc-ingress wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
|Status=No
}}{{Section
|sectionHeading=Deploy in OpenShift
|alignment=Vertical
|structuredtext=You need to use PersistentVolume and PersistentVolumeClaim instead of HostPath logs of Gateway pods and CoTurn Pods.
|Status=No
}}{{Section
|sectionHeading=Validate the deployment in OpenShift
|alignment=Vertical
|structuredtext={{Notices|Notice=PEComingSoon}}
|Status=No
}}
|PEPageType=45d1441f-dc69-4a17-bd47-af5d811ce167
}}

@@ Line 123: / Line 123: @@
 |Status=No
 }}{{Section
-|sectionHeading=Deploy in OpenShift
+|sectionHeading=Deploy
 |alignment=Vertical
 |structuredtext=You need to use PersistentVolume and PersistentVolumeClaim instead of HostPath logs of Gateway pods and CoTurn Pods.
 |Status=No
 }}{{Section
-|sectionHeading=Validate the deployment in OpenShift
+|sectionHeading=Validate the deployment
 |alignment=Vertical
 |structuredtext=Follow the steps given below to validate the deployment in OpenShift
 #'''Verify PVCs are created and bound'''
-#:<source lang="LANGUAGE">oc get pvc</source>
+#:<source lang="LANGUAGE">kubectl get pvc</source>
 #:Sample output:
 #:<source lang="LANGUAGE">NAME                     STATUS   VOLUME                      CAPACITY   ACCESS MODES   STORAGECLASS     AGE
@@ Line 139: / Line 139: @@
 webrtc-gateway-log-pvc   Bound    webrtc-gateway-log-volume   5Gi        RWX            genesys-webrtc   110s</source>
 #'''Validate CoTurn and Gateway services'''
-#:<source lang="LANGUAGE">oc get svc</source>
+#:<source lang="LANGUAGE">kubectl get svc</source>
 #:Sample output:
 #:<source lang="LANGUAGE">NAME                          TYPE           CLUSTER-IP      EXTERNAL-IP      PORT(S)           AGE
@@ Line 145: / Line 145: @@
 webrtc-gateway-service-blue   ClusterIP      10.202.47.170   <none>           80/TCP,8080/TCP   67m</source>
 #'''Query pods in the WebRTC namespace to confirm that pod is created, and in running status'''
-#:<source lang="LANGUAGE">oc get pods</source>
+#:<source lang="LANGUAGE">kubectl get pods</source>
 #:Sample output:
 #:<source lang="LANGUAGE">NAME                                  READY   STATUS    RESTARTS   AGE
@@ Line 151: / Line 151: @@
 webrtc-gateway-blue-d7ff45677-vbdg9   1/1     Running   0          86s</source>
 #'''Validate Ingress configuration'''
-#:<source lang="LANGUAGE">oc get ingress</source>
+#:<source lang="LANGUAGE">kubectl get ingress</source>
 #:Sample output:
 #:<source lang="LANGUAGE">NAME                 CLASS    HOSTS                                                                        ADDRESS   PORTS   AGE
 webrtc-ingress-int   <none>   webrtc.apps.vce-c0.eps.genesys.com,webrtc-test.apps.vce-c0.eps.genesys.com             80      68s</source>
 #Validate Ingress Edge route configuration
-#:<source lang="LANGUAGE">oc get route</source>
+#:<source lang="LANGUAGE">kubectl get route</source>
 #:Sample output:
 #:<source lang="LANGUAGE">NAME                          HOST/PORT                                     PATH    SERVICES                      PORT   TERMINATION   WILDCARD
@@ Line 164: / Line 164: @@
 webrtc-ingress-int-wf6x9      webrtc-test.apps.qrtph6qa.westus2.aroapp.io   /blue   webrtc-gateway-service-blue   web                  None</source>
 #'''Query Ingress for exposed WebRTC Web API'''
-#:<source lang="LANGUAGE">oc get ingress</source>
+#:<source lang="LANGUAGE">kubectl get ingress</source>
 #:Copy the WebRTC API from the Ingress output:
 #:Sample output:

@@ Line 1: / Line 1: @@
-{{Article
+{{ArticlePEServiceDeploy
-|Standalone=No
+|ServiceId=12d65e68-20aa-4cf7-848f-cc4358c67b25
-|DisplayName=Deploy WebRTC
+|IncludeAssumptions=Yes
 |Section={{Section
 |alignment=Vertical
@@ Line 13: / Line 11: @@
 **'''webrtc.domain.com''' - active deployment. For example: webrtc.genesyshtcc.com
 **'''webrtc-test.domain.com''' - inactive deployment for tests. For example: webrtc-test.genesyshtcc.com
+|Status=No
-You can deploy WebRTC using:
+}}{{Section
 *Internal CoTurn Load Balancer or
@@ Line 20: / Line 21: @@
 ===Deploying WebRTC using internal CoTurn Load Balancer===
 Initial deployment and Upgrade use the same sequence:
 #Deploy/upgrade inactive color of deployment
 #Make the cutover
-You need to deploy the Color Infra package with CoTurn Load Balancer to get the IP address assigned automatically for the CoTurn Load Balancer by the infrastructure. Then, the infrastructure team should assign the IP to the CoTurn Load Balancer, create the FQDN for the IP and ensure that the IP is set in the firewall and is available from outside the cluster.
+You need to deploy the Color Infra package with CoTurn Load Balancer to get the IP address assigned automatically for the CoTurn Load Balancer by the infrastructure. Then, the infrastructure team should assign the IP to the CoTurn Load Balancer, create the FQDN for the IP and ensure that the IP is set in the firewall and is available from outside the cluster.{{NoteFormat|The IP address assigned to the CoTurn Load Balancer must be external and available outside the cluster. Else, the media will not get through the WebRTC.|}}The following image shows the steps involved in deploying WebRTC using the internal CoTurn Load Balancer:
-[[File:WebRTC-Internal-Deployment.png]]
+[[File:WebRTC-Internal-Deployment.png|link=https://all.docs-qa.genesys.com/File:WebRTC-Internal-Deployment.png]]
 Follow the below steps to deploy WebRTC using internal CoTurn Load Balancer:
@@ Line 53: / Line 52: @@
 #:Example:
 #:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=coturn --set-string deployment.color=blue webrtc-coturn-blue wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>
-#'''Create Gateway elements for deployment color using the information from Step 3''': This step is to Upgrade/Deploy Gateway for INACTIVE color. You shoud also specify the extenal FQDN of the CoTurn LoadBalancer in this step using the <tt>gateway.turnExternalUriBlue</tt> or <tt>gateway.turnExternalUriGreen</tt> options.
+#'''Create Gateway elements for deployment color using the information from Step 3''': This step is to Upgrade/Deploy Gateway for INACTIVE color. You shoud also specify the extenal FQDN of the CoTurn LoadBalancer in this step using the <code>gateway.turnExternalUriBlue</code> or <code>gateway.turnExternalUriGreen</code> options.
 #:Run the following command:
 #:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=gateway --set-string deployment.color={INACTIVE_COLOR} --set-string gateway.turnExternalUri{INACTIVE_COLOR}={COTURN FQDN INACTIVE_COLOR} webrtc-gateway-{INACTIVE_COLOR} {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>
@@ Line 69: / Line 68: @@
 ===Deployment with external CoTurn Load Balancer===
 Initial deployment and Upgrade use the same sequence:
 #Deploy/upgrade inactive color of deployment
@@ Line 76: / Line 75: @@
 The following image shows the steps involved in deploying WebRTC using the external CoTurn Load Balancer:
-[[File:WebRTC-External-Deployment-1.png]]
+[[File:WebRTC-External-Deployment-1.png|link=https://all.docs-qa.genesys.com/File:WebRTC-External-Deployment-1.png]]
 Follow the below steps to deploy WebRTC with external CoTurn Load Balancer
-#'''Create static IPs for CoTurn''': This step is to specify the pre-created public IP for CoTurn Green in the <tt>coturn.lbIpGreen</tt> option and public IP for CoTurn Blue in the <tt>coturn.lbIpBlue</tt> option.
+#'''Create static IPs for CoTurn''': This step is to specify the pre-created public IP for CoTurn Green in the <code>coturn.lbIpGreen</code> option and public IP for CoTurn Blue in the <code>coturn.lbIpBlue</code> option.
-#'''Create DNS records for the created IPs''': This step is to specify the public FQDNs for CoTurn. Specify the pre-created public FQDN for CoTurn Green in the <tt>gateway.turnExternalUriGreen</tt> option and public FQDN for CoTurn Blue in the <tt>gateway.turnExternalUriBlu</tt>e option.
+#'''Create DNS records for the created IPs''': This step is to specify the public FQDNs for CoTurn. Specify the pre-created public FQDN for CoTurn Green in the <code>gateway.turnExternalUriGreen</code> option and public FQDN for CoTurn Blue in the <code>gateway.turnExternalUriBlu</code>e option.
 #'''Create common infrastructure elements''': This step will deploy Persistent Volumes, Persistent Volume Claims, dashboards, alarms, and other common infrastructure elements.
 #:{{NoteFormat|You need to run this step even if you are not using the dashboard and alarms.}}
@@ Line 115: / Line 114: @@
 ===Cutover===
-During cutover, it switches active color of deployment. This step should be performed only after you confirm that the newly installed/upgraded deployment is alive and functional.
+During cutover, it switches active color of deployment. This step should be performed only after you confirm that the newly installed/upgraded deployment is alive and functional. You must specify the current INACTIVE color of deployment in the <code>deployment.color</code> option - deployment that was just deployed/upgraded and tested. Run the following command to specify the cutover:<source lang="LANGUAGE">helm upgrade --install -f {Webrtc Values files} --set-string deployment.type=cutover --set-string deployment.color={INACTIVE_COLOR} webrtc-ingress {HelmRepoPath }/webrtc-service --version={WebRTC Charts Version}</source>Example:<source lang="LANGUAGE">helm upgrade --install -f ./k8s/values.yaml --set-string deployment.type=cutover --set-string deployment.color=blue webrtc-ingress wrtchelmrepodevwestus2/webrtc-service --version=0.1.93 -n webrtc</source>{{NoteFormat|You need to use PersistentVolume and PersistentVolumeClaim instead of HostPath logs of Gateway pods and CoTurn Pods.|}}
 |Status=No
 }}{{Section
 |sectionHeading=Validate the deployment
 |alignment=Vertical
-|structuredtext=Follow the steps given below to validate the deployment in OpenShift
+|structuredtext=Follow the given steps to validate the deployment.
 #'''Verify PVCs are created and bound'''
@@ Line 163: / Line 152: @@
 webrtc-ingress-int-trcvh      webrtc.apps.qrtph6qa.westus2.aroapp.io        /blue   webrtc-gateway-service-blue   web                  None
 webrtc-ingress-int-wf6x9      webrtc-test.apps.qrtph6qa.westus2.aroapp.io   /blue   webrtc-gateway-service-blue   web                  None</source>
-#'''Query Ingress for exposed WebRTC Web API'''
+#'''Query Ingress for''' made available '''WebRTC Web API'''
 #:<source lang="LANGUAGE">kubectl get ingress</source>
 #:Copy the WebRTC API from the Ingress output: