Configure <service_name>
From Genesys Documentation
This is a draft page; it has not yet been published.
Learn how to configure <service_name>.
Related documentation:
Override Helm chart values
Link to the "suite-level" documentation about how to override Helm chart values:
#mintydocs_link must be called from a MintyDocs-enabled page (Draft:PEC-REP/Current/RAAPEGuide/Configure).
If there are multiple YAML files (for example, one for each container if your service has multiple containers), you could use a table for each file or use a single table with an extra column for the file name. If the parameter is related to a feature documented elsewhere, you can include a link in the Description column. For example, descriptions for logging setting can link to the Logging page.
Note: We are still working on an approach to handle documentation for Helm chart values, so please leave this section until the end.
| Parameter | Description | Default | Valid values |
|---|---|---|---|
| service.port | Designer service to be exposed. | 8888 | A valid port. |
| ... |
Configure Kubernetes
Document the layouts for the following so customers can create them if their Helm chart doesn't include a way to do this:
- ConfigMaps
- Secrets
Configure security
List security-related settings, such as how to set up credentials and certificates for third-party services.