PrivateEdition/Current/PEGuide/Prerequisites - Revision history

WikiSysop at 08:01, July 5, 2023

2023-07-05T08:01:08Z

WikiSysop at 03:31, March 31, 2023

2023-03-31T03:31:52Z

WikiSysop at 14:01, March 23, 2023

2023-03-23T14:01:10Z

WikiSysop at 19:01, March 22, 2023

2023-03-22T19:01:10Z

WikiSysop at 13:00, November 9, 2022

2022-11-09T13:00:42Z

WikiSysop at 14:31, October 27, 2022

2022-10-27T14:31:56Z

WikiSysop at 06:30, September 29, 2022

2022-09-29T06:30:49Z

WikiSysop at 14:00, August 2, 2022

2022-08-02T14:00:55Z

WikiSysop at 17:30, May 17, 2022

2022-05-17T17:30:43Z

Uma.jayakumar.IX: Published

2021-12-22T18:59:51Z

Published

@@ Line 25: / Line 25: @@
 <!-- **OpenShift Ingress Controller (OpenShift Container Platform) -->
 *JFrog Edge Artifactory account
-*Kubernetes 1.24
+*Kubernetes 1.25
 *Kubernetes secrets<!-- for OpenShift deployments-->
 *Session Border Controller (SBC)

@@ Line 23: / Line 23: @@
 *Ingress Controller
 **NGINX Ingress Controller (Google Kubernetes Engine)
-**OpenShift Ingress Controller (OpenShift Container Platform)
+<!-- **OpenShift Ingress Controller (OpenShift Container Platform) -->
 *JFrog Edge Artifactory account
 *Kubernetes 1.24
-*Kubernetes secrets for OpenShift deployments
+*Kubernetes secrets<!-- for OpenShift deployments-->
 *Session Border Controller (SBC)
 *Web Application Firewall (WAF) - optional, but recommended.
@@ Line 41: / Line 41: @@
 See the table below for details about the Genesys supported third-party dependencies.
 {{SuiteThirdPartyTable}}
 {{NoteFormat|For OpenShift deployments, Genesys has tested the OpenShift Operators listed in the table, but you can check with Genesys regarding replacing them with other cloud managed services (such as, Azure Postgres or AWS RDS Postgres). You could also run these services outside of OpenShift if you prefer.}}
+-->
 For information on troubleshooting third-party services, refer to [https://github.com/genesys/multicloud-services/wiki#third-party-services Troubleshooting Third-Party Services] in our public repository.
 |Status=No
@@ Line 49: / Line 50: @@
 |anchor=Permissions
 |alignment=Vertical
-|structuredtext=Security context parameters in the Helm charts specify the users authorized to access the pods and containers for the respective services. By default, the Helm charts specify the user, group, and file-service group IDs as <tt>500:500:500.</tt> Genesys recommends to use [[{{FULLPAGENAME}}#ArbitraryUIDs|Arbitrary UIDs]] in OpenShift.
+|structuredtext=Security context parameters in the Helm charts specify the users authorized to access the pods and containers for the respective services. By default, the Helm charts specify the user, group, and file-service group IDs as <tt>500:500:500.</tt> <!-- Genesys recommends to use [[{{FULLPAGENAME}}#ArbitraryUIDs|Arbitrary UIDs]] in OpenShift.-->
 ===Consul===
@@ Line 55: / Line 56: @@
 *Consul and Consul Service Mesh are required.
 *Consul requires privileged containers; so the cluster-administrator must have permissions to install mutating hooks, configure kube-dns, and access Kubernetes APIs.
+<!--
 ===OpenShift===
 OpenShift controls the pod permissions (including user access) through a security feature called ''security context constraints'' (SCCs). Private edition supports the use of arbitrary user IDs (UIDs), with pods and containers using the '''restricted''' SCC (the most restrictive SCC defined by default).
 In an early implementation, private edition required the use of a custom SCC called '''genesys-restricted''' to control permissions associated with the '''genesys''' user (500) specified by the services. The '''genesys-restricted''' SCC has now been deprecated.
@@ Line 63: / Line 65: @@
 {{AnchorDiv|ArbitraryUIDs}}
 ====Arbitrary UIDs====
-To use arbitrary UIDs, override the Helm chart values so that no specific IDs are defined for users and groups. See {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ConfigSecurity}} for more information.
+To use arbitrary UIDs, override the Helm chart values so that no specific IDs are defined for users and groups.
 |Status=No
 }}
 }}

@@ Line 25: / Line 25: @@
 **OpenShift Ingress Controller (OpenShift Container Platform)
 *JFrog Edge Artifactory account
-*Kubernetes 1.24 (see [[{{FULLPAGENAME}}#KubernetesDistributions|Supported Kubernetes distributions]])
+*Kubernetes 1.24
 *Kubernetes secrets for OpenShift deployments
 *Session Border Controller (SBC)
 *Web Application Firewall (WAF) - optional, but recommended.
 ===Licensing requirements===

@@ Line 25: / Line 25: @@
 **OpenShift Ingress Controller (OpenShift Container Platform)
 *JFrog Edge Artifactory account
-*Kubernetes 1.23 (see [[{{FULLPAGENAME}}#KubernetesDistributions|Supported Kubernetes distributions]])
+*Kubernetes 1.24 (see [[{{FULLPAGENAME}}#KubernetesDistributions|Supported Kubernetes distributions]])
 *Kubernetes secrets for OpenShift deployments
 *Session Border Controller (SBC)

@@ Line 25: / Line 25: @@
 **OpenShift Ingress Controller (OpenShift Container Platform)
 *JFrog Edge Artifactory account
-*Kubernetes 1.22 (see [[{{FULLPAGENAME}}#KubernetesDistributions|Supported Kubernetes distributions]])
+*Kubernetes 1.23 (see [[{{FULLPAGENAME}}#KubernetesDistributions|Supported Kubernetes distributions]])
 *Kubernetes secrets for OpenShift deployments
 *Session Border Controller (SBC)
@@ Line 34: / Line 34: @@
 Currently, Genesys supports the following Kubernetes distributions as part of the cloud private edition offering. If you are looking for other Kubernetes distributions, contact your Genesys Account Representative.
-*Azure Kubernetes Service 1.22
+*Google Kubernetes Engine 1.22 and 1.23
 ===Licensing requirements===
@@ Line 52: / Line 50: @@
 For information on troubleshooting third-party services, refer to [https://github.com/genesys/multicloud-services/wiki#third-party-services Troubleshooting Third-Party Services] in our public repository.
 |Status=No
 }}{{Section