Trust manager custom resource fields
You can configure the behavior of the trust-manager operand by modifying the TrustManager custom resource (CR).
|
|
Distributing certificates by using trust manager is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope. |
The following table lists the parameters for configuring trust-manager settings.
| Field | Type | Description | ||
|---|---|---|---|---|
|
|
Optional. Specifies a list of key-value pairs to apply as labels to all resources created for the trust manager deployment. |
||
|
|
Optional. Specifies a list of key-value pairs to apply as annotations to all resources created for the trust manager deployment. |
||
|
|
Optional. Specifies the scheduling constraints for the trust manager pod. For more information, see Assigning Pods to Nodes. |
||
|
|
Optional. Configures the default CA package for trust manager. When enabled, the Operator uses the Red Hat OpenShift Container Platform trusted CA bundle injection mechanism. |
||
|
|
Optional. Specifies whether the default CA package feature is enabled. When set to
|
||
|
|
Optional. Specifies whether trust manager filters out expired certificates from trust bundles before distributing them. When set to |
||
|
|
Optional. Specifies the verbosity of trust manager logging. The minimum value is |
||
|
|
Optional. Specifies the output format for trust manager logging. The supported formats are |
||
|
|
Optional. Specifies the key-value pairs that limit which nodes can host the trust manager pod. You can specify a maximum of 50 node selectors. For more information, see Assigning Pods to Nodes. |
||
|
|
Optional. Defines the compute resource requirements for the trust manager pod. |
||
|
|
Optional. Defines the configuration for writing trust bundles to |
||
|
|
Optional. A list of specific secret names that trust manager is authorized to create and update.
|
||
|
|
Optional. Specifies whether trust manager can write trust bundles to |
||
|
|
Optional. Allows the trust manager pod to be scheduled on nodes with specific taints. You can specify a maximum of 50 tolerations. |
||
|
|
Optional. Specifies the namespace where trust manager locates CA certificate sources, such as ConfigMaps and Secrets. This namespace must exist before you create the TrustManager custom resource. The default value is
|