GWS/Current/GWSPEGuide/DeployIngress - Revision history

WikiSysop at 13:01, February 28, 2023

2023-02-28T13:01:40Z

WikiSysop at 13:15, July 22, 2022

2022-07-22T13:15:54Z

Jumunn: Published

2022-07-08T16:26:53Z

Published

WikiSysop at 12:45, April 26, 2022

2022-04-26T12:45:54Z

Jumunn: Published

2022-02-01T20:18:56Z

Published

Julie.munn@genesys.com at 20:56, October 29, 2021

2021-10-29T20:56:12Z

Julie.munn@genesys.com: Published

2021-10-29T20:55:44Z

Published

Show changes

Julie.munn@genesys.com at 12:46, July 21, 2021

2021-07-21T12:46:44Z

Monique.gionet@genesys.com: Published

2021-06-30T15:38:08Z

Published

Monique.gionet@genesys.com: Published

2021-06-30T15:32:30Z

Published

@@ Line 18: / Line 18: @@
 |alignment=Vertical
 |structuredtext=To deploy GWS ingress, you need the GWS ingress Helm package and override file. Copy '''values.yaml''' and the Helm package ('''gws-ingress-<version>.tgz''') to the installation location.
+<!--
 For OpenShift, select the '''gws''' project you created in {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy|anchor=OpenShift|display text=Prepare your environment}}:
   oc project gws
 Run the following command to deploy GWS ingress:
   helm upgrade --install gws-ingress <helm_directory>/gws-ingress --version=<version> -n gws -f ./override.gws-ingress.values.yaml -f ./versions.yaml
 |Status=No
-}}{{Section
+}}
 |sectionHeading=Create routes in OpenShift
 |anchor=https
@@ Line 34: / Line 37: @@
   oc create route edge --service=gws-service-proxy --hostname=<hostname>
 |Status=No
-}}{{Section
+}}
 |sectionHeading=Validate the deployment
 |alignment=Vertical

@@ Line 1: / Line 1: @@
 {{ArticlePEServiceDeploy
 |ServiceId=11ff3d39-ae2b-4526-b7e5-7dcdf781ef01
-|IncludedServiceId=1dd952ea-ff42-44ac-9046-ca5786df98c8
+|IncludedServiceId=8d3bb679-8e6d-4070-b73b-9c956a21588a
 |IncludeAssumptions=Yes
 |Section={{Section

@@ Line 5: / Line 5: @@
 |Section={{Section
 |alignment=Vertical
-|structuredtext={{NoteFormat|If you are deploying Web Services and Applications in a single namespace with other private edition services, then you do not need to deploy GWS ingress.|3}}
+|structuredtext={{NoteFormat|If you are deploying Genesys Web Services and Applications in a single namespace with other private edition services, then you do not need to deploy GWS ingress.|3}}
 |Status=No
 }}{{Section
@@ Line 11: / Line 11: @@
 |anchor=prerequisites
 |alignment=Vertical
-|structuredtext=Before you deploy GWS Ingress, you must first {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}} and {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}.
+|structuredtext=Before you deploy GWS ingress, you must first {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}} and {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}.
 |Status=No
 }}{{Section
@@ Line 17: / Line 17: @@
 |anchor=deploy
 |alignment=Vertical
-|structuredtext=To deploy GWS Ingress, you need the GWS Ingress Helm package and override file. Copy '''values.yaml''' and the Helm package ('''gws-ingress-<version>.tgz''') to the installation location.
+|structuredtext=To deploy GWS ingress, you need the GWS ingress Helm package and override file. Copy '''values.yaml''' and the Helm package ('''gws-ingress-<version>.tgz''') to the installation location.
 For OpenShift, select the '''gws''' project you created in {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy|anchor=OpenShift|display text=Prepare your environment}}:

@@ Line 1: / Line 1: @@
-{{Article
+{{ArticlePEServiceDeploy
-|Standalone=No
+|ServiceId=11ff3d39-ae2b-4526-b7e5-7dcdf781ef01
-|DisplayName=Deploy GWS Ingress
+|IncludedServiceId=1dd952ea-ff42-44ac-9046-ca5786df98c8
-|Context=Learn how to deploy GWS Ingress.
+|IncludeAssumptions=Yes
 |Section={{Section
 |alignment=Vertical
@@ Line 84: / Line 83: @@
 |anchor=next
 |alignment=Vertical
-|structuredtext=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ProvisionAS}}
+|structuredtext=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Provision}}
 |Status=No
 }}
 }}

@@ Line 5: / Line 5: @@
 |ComingSoon=No
 |Section={{Section
 |sectionHeading=Prerequisites
 |anchor=prerequisites
 |alignment=Vertical
-|structuredtext=Before you deploy GWS Ingress, you must first {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}}.
+|structuredtext=Before you deploy GWS Ingress, you must first {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}} and {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}.
 |Status=No
 }}{{Section
@@ Line 19: / Line 23: @@
   oc project gws
 Run the following command to deploy GWS ingress:
-  helm upgrade --install gws-ingress helm-staging/gws-ingress --version=<version> -n gws -f ./override.gws-ingress.values.yaml -f ./versions.yaml
+  helm upgrade --install gws-ingress <helm_directory>/gws-ingress --version=<version> -n gws -f ./override.gws-ingress.values.yaml -f ./versions.yaml
 |Status=No
 }}{{Section
-|sectionHeading=Configure external access
+|sectionHeading=Create routes in OpenShift
 |anchor=https
 |alignment=Vertical
-|structuredtext=Follow the instructions for either OpenShift or GKE to configure external access to GWS ingress.
+|structuredtext=Follow the instructions to configure external access to GWS ingress in OpenShift.
 Genesys recommends using the following hostname format: <code>gws.<cluster-subdomain></code>. For example, the VCE cluster (<nowiki>https://console-openshift-console.apps</nowiki>.<yourclusterdomain>.com/) should have the hostname '''gws.<yourclusterdomain>.com'''
   oc create route edge --service=gws-service-proxy --hostname=<hostname>
 |Status=No
 }}{{Section
@@ Line 153: / Line 79: @@
   kubectl get all -n gws
 The result should show all the created pods, services, ConfigMaps, and so on.
 |Status=No
 }}{{Section