5.3.4. Configuration parameters for MustGather custom resource
You can manage your MustGather custom resource (CR) by creating a YAML file that specifies the parameters for data collection and the upload process. The following table provides an overview of the parameters that you can configure in the MustGather CR.
| Parameter name | Description | Type |
|---|---|---|
|
|
Optional: Specifies whether to collect audit logs. The valid values are |
|
|
|
Optional: Specifies the time limit for the |
The value must be a floating-point number with a time unit. The valid units are |
|
| Optional: Defines the proxy configuration to be used. The default value is set to the cluster-level proxy configuration. |
|
|
| Specifies the URL of the proxy for HTTP requests. | URL |
|
| Specifies the URL of the proxy for HTTPS requests. | |
|
| Specifies a comma-separated list of domains for which the proxy must not be used. | List of URLs |
|
|
Optional: Specifies whether to retain the |
|
|
|
Optional: Specifies the name of the service account. The default value is |
|
|
|
Optional: Defines the storage configuration for the |
|
|
| Defines the details of the persistent volume. |
|
|
| Defines the details of the persistent volume claim (PVC). |
|
|
| Specifies the name of the PVC to be used for storage. |
|
|
| Optional: Specifies the path within the PVC to store the bundle. |
|
|
|
Defines the type of storage. The only supported value is |
|
|
|
Optional: Defines the upload location for the |
|
|
|
Optional: Specifies the destination server for the bundle upload. By default, the bundle is uploaded to |
By default, the bundle is uploaded to |
|
| Specifies the Red Hat Support case ID for which the diagnostic data is collected. |
|
|
|
Defines the credentials required for authenticating and uploading the files to the Red Hat Customer Portal support case. The value must contain a |
|
|
| Specifies the name of the Kubernetes secret that contains the credentials. |
|
|
|
Optional: Specifies whether the user provided in the |
|
|
|
Specifies the type of upload location for the |
|
If you do not specify spec.uploadTarget or spec.storage, the pod saves the data to an ephemeral volume and the data is permanently deleted when the pod terminates.