Difference between revisions of "Template: Fad4ebcb-b064-4403-88b0-61809001e2cb"
From Genesys Documentation
(Created page with "== Assumptions == *The instructions on this page assume you are deploying the service in a service-specific namespace or OpenShift project, named in accordance with the requir...") |
|||
| Line 1: | Line 1: | ||
== Assumptions == | == Assumptions == | ||
| − | *The instructions on this page assume you are deploying the service in a service-specific namespace | + | *The instructions on this page assume you are deploying the service in a service-specific namespace, named in accordance with the requirements on {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigNamespace}}. If you are using a single namespace for all private edition services, replace the namespace element in the commands on this page with the name of your single namespace or project. |
*Similarly, the configuration and environment setup instructions assume you need to create namespace-specific (in other words, service-specific) secrets. If you are using a single namespace for all private edition services, you might not need to create separate secrets for each service, depending on your credentials management requirements. However, if you do create service-specific secrets in a single namespace, be sure to avoid naming conflicts. | *Similarly, the configuration and environment setup instructions assume you need to create namespace-specific (in other words, service-specific) secrets. If you are using a single namespace for all private edition services, you might not need to create separate secrets for each service, depending on your credentials management requirements. However, if you do create service-specific secrets in a single namespace, be sure to avoid naming conflicts. | ||
Latest revision as of 12:30, February 20, 2023
Assumptions[edit source]
- The instructions on this page assume you are deploying the service in a service-specific namespace, named in accordance with the requirements on #mintydocs_link must be called from a MintyDocs-enabled page (Template:Fad4ebcb-b064-4403-88b0-61809001e2cb).. If you are using a single namespace for all private edition services, replace the namespace element in the commands on this page with the name of your single namespace or project.
- Similarly, the configuration and environment setup instructions assume you need to create namespace-specific (in other words, service-specific) secrets. If you are using a single namespace for all private edition services, you might not need to create separate secrets for each service, depending on your credentials management requirements. However, if you do create service-specific secrets in a single namespace, be sure to avoid naming conflicts.