TLM/Current/TLMPEGuide/Deploy - Revision history

WikiSysop at 08:32, February 28, 2023

2023-02-28T08:32:08Z

WikiSysop at 16:32, September 29, 2022

2022-09-29T16:32:17Z

Show changes

Xavier: Published

2021-12-22T17:20:24Z

Published

Xavier.roy@genesys.com: Published

2021-06-30T11:25:17Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Deploy Telemetry Service
|Context=Learn how to deploy Telemetry Service.
|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 Telemetry Service.|}}
|Status=No
}}{{Section
|sectionHeading=Deploy in OpenShift
|alignment=Vertical
|structuredtext=To install the Telemetry Service, run the following command:
<pre>helm install -f values-tlm.yaml telemetry-service telemetry-service/</pre>
|Status=No
}}{{Section
|sectionHeading=Validate the deployment in OpenShift
|alignment=Vertical
|structuredtext=To validate the installed release, run the following command:
<pre>helm list –n tlm</pre>
Verify that details of the Telemetry Service deployment information is displayed.

To check the installed Helm release, execute the following command:
<pre>helm list –n tlm</pre>
Verify that the deployment status mentions 'STATUS: deployed'.
<br />
|Status=No
}}
|PEPageType=45d1441f-dc69-4a17-bd47-af5d811ce167
}}

@@ Line 117: / Line 117: @@
 Use the following commands to create the Secret for accessing the jfrog registry and map the secret to the default account:<source lang="Emacs">
-oc create secret docker-registry mycred --docker-server=pureengageuse1-docker-multicloud.jfrog.io --docker-username=<camelot-username> --docker-password=<API key from jfrog> --docker-email=<emailid>
+kubectl create secret docker-registry mycred --docker-server=pureengageuse1-docker-multicloud.jfrog.io --docker-username=<camelot-username> --docker-password=<API key from jfrog> --docker-email=<emailid>
 </source>
@@ Line 397: / Line 395: @@
 </source>
 ====Validate the deployment====
-Use the following command to verify that the new route is created in the Telemetry Service project on OpenShift:<source lang="Emacs">
+Use the following command to verify that the new route is created in the Telemetry Service project:<source lang="Emacs">
 kubectl get ingress -n tlm (ingress information appears, similar to the following)

@@ Line 9: / Line 9: @@
 |Status=No
 }}{{Section
-|sectionHeading=Deploy in OpenShift
+|sectionHeading=Deploy the service
 |alignment=Vertical
 |structuredtext=To install the Telemetry Service, run the following command:
@@ Line 15: / Line 15: @@
 |Status=No
 }}{{Section
-|sectionHeading=Validate the deployment in OpenShift
+|sectionHeading=Validate the deployment
 |alignment=Vertical
 |structuredtext=To validate the installed release, run the following command:
-<pre>helm list –n tlm</pre>
+<source lang="text">helm list –n tlm</source>
 Verify that details of the Telemetry Service deployment information is displayed.
-To check the installed Helm release, execute the following command:
+To check the status of installed Helm release, execute the following command:
-<pre>helm list –n tlm</pre>
+<source lang="text">helm status telemetry-service -n tlm</source>
 Verify that the deployment status mentions 'STATUS: deployed'.
 <br />
 |Status=No