Task Manager parameters
Update the custom YAML file to provide the details that are relevant to your Task Manager and your decisions for the deployment of the container.
| Parameters | Description | Default or Example Values | |
|---|---|---|---|
| resources.requests.ephemeral_storage | Specifies an ephemeral storage request for the container. | No | |
| resources.limits.ephemeral_storage | Specifies an ephemeral storage limit for the container. | No | |
| arch.amd64 | The architecture for your environment. | 3 - Most preferred | Yes, leave default |
| replica_count | How many Content Platform Engine replicas to deploy. | 2 | No |
| image.repository | The repository to use. | cp.icr.io/cp/cp4a/fncm/taskmgr | No |
| image.tag | The specific tag for your release. | ga-30x-tm | No |
| image.pull_policy | The pull policy for the image. | IfNotPresent | No |
| resources.requests.cpu | Specifies a CPU request for the container. | 500m | No |
| resources.requests.memory | Specify a memory request for the container. | 512Mi | No |
| resources.limits.cpu | Specify a CPU limit for the container. | 1 | No |
| resources.limits.memory | Specify a memory limit for the container. | 1536Mi | No |
| auto_scaling.enabled | Specify whether to enable auto scaling. | false | No |
| auto_scaling.max_replicas | The upper limit for the number of pods that can be set by the autoscaler. Required. | 3 | No |
| auto_scaling.min_replicas | The lower limit for the number of pods that can be set by the autoscaler. If it is not specified or negative, the server will apply a default value. | 2 | No |
| auto_scaling.target_cpu_utilization_percentage | The target average CPU utilization (represented as a percent of requested CPU) over all the pods. If it is not specified or negative, a default autoscaling policy is used. | 80 | No |
| hostname | External hostname for the service. The hostname can consist of lowercase alphanumeric
characters or '-', and must start and end with an alphanumeric character. If not specified, hostname
is generated from shared_configuration.sc_deployment_hostname_suffix. |
new-hostname | No |
| probe.startup.initial_delay_seconds | The behavior of startup probes to know when the container is started. | 120 | No |
| probe.startup.period_seconds | The period in seconds. | 10 | No |
| probe.startup.timeout_seconds | The timeout setting in seconds. | 10 | No |
| probe.startup.failure_threshold | The threshold number for failures. | 6 | No |
| tm_production_setting.time_zone | The time zone for the container deployment. | Etc/UTC | No |
| tm_production_setting.jvm_initial_heap_percentage | The initial use of available memory. | 40 | No |
| tm_production_setting.jvm_max_heap_percentage | The maximum percentage of available memory to use. | 66 | No |
| tm_production_setting.jvm_customize_options | Optionally specify JVM arguments using comma separation. For example: jvm_customize_options="-Dmy.test.jvm.arg1=123,-Dmy.test.jvm.arg2=abc,-XX:+SomeJVMSettings,-XshowSettings:vm" If needed, you can use DELIM to change the character that is used to separate multiple JVM arguments. In this example, a semi-colon is used to separate the JVM arguments: jvm_customize_options="DELIM=;-Dcom.filenet.authentication.wsi.AutoDetectAuthToken=true;-Dcom.filenet.authentication.providers=ExShareUmsInternal,ExShareIbmId,ExShareGID" |
"-Dcom.ibm.ecm.task.StartUpListener.defaultLogLevel=FINE" | No |
| tm_production_setting.license | The value must be set to accept to deploy. | accept | Yes |
| tm_production_setting.custom_configmap.name | The name of the custom configmap. | custom-navigator-config-files | Yes |
| tm_production_setting.custom_configmap.volume_path | The location you want to hold files in. | No | |
| tm_production_setting.custom_configmap.is_env | Specify whether the config map holds environment variables. | false | Required only when configmap holds data information. |
| tm_production_setting.security_roles_to_group_mapping.task_admins groups users |
The names of customizable admin user roles and groups. Defining both groups and users is not necessary as long as at least one is defined. |
taskAdmins admin1, admin2 |
If you do not define values, the default values of taskAdmins will be assigned. |
| tm_production_setting.security_roles_to_group_mapping.task_users
groups users |
The names of customizable user roles and groups. Defining both groups and users is not necessary as long as at least one is defined. |
task_users user1, user2 |
If you do not define values, the default values of task_users will be assigned. |
| tm_production_setting.security_roles_to_group_mapping.task_auditors groups users |
The names of customizable auditor user roles and groups. Defining both groups and users is not necessary as long as at least one is defined. |
task_auditors auditor1, auditor2 |
If you do not define values, the default values of task_auditors will be assigned. |
| monitor_enabled | Specify whether to use the built-in monitoring capability. | false | No |
| logging_enabled | Specify whether to use the built-in logging capability. | false | No |
| collectd_enable_plugin_write_graphite | If you use Graphite database for metrics or use IBM Cloud® monitoring, set to true. | false | No |
| datavolume.existing _pvc_for_tm_cfgstore.name | The persistent volume claim for Task Manager configuration. | tm-cfgstore | Yes if you want to use existing PVC |
| datavolume.existing _pvc_for_tm_cfgstore.size | The persistent volume claim size for Task Manager configuration. | 1Gi | No |
| datavolume.existing _pvc_for_tm_logstore.name | The persistent volume claim for Task Manager logs. | tm-logstore | Yes if you want to use existing PVC |
| datavolume.existing _pvc_for_tm_logstore.size | The persistent volume claim size for Task Manager logs. | 1Gi | No |
| datavolume.existing_pvc_for_tm_pluginstore.name | The persistent volume claim for the Task Manager plug in. | tm-pluginstore | Yes if you want to use existing PVC |
| datavolume.existing_pvc_for_tm_pluginstore.size | The persistent volume claim size for the Task Manager plug in. | 1Gi | No |
| probe.readiness.period_seconds | The period in seconds. | 10 | No |
| probe.readiness.timeout_seconds | The timeout setting in seconds. | 10 | No |
| probe.readiness.failure_threshold | The threshold number for failures. | 6 | No |
| probe.liveness.period_seconds | The period in seconds. | 10 | No |
| probe.liveness.timeout_seconds | The timeout setting in seconds. | 5 | No |
| probe.liveness.failure_threshold | The threshold number for failures. | 6 | No |
| image_pull_secrets.name | The secrets to be able to pull images. | admin.registrykey | Yes, only if you want to override the comparable setting in the shared configuration section. |