dkp check cluster fips
Validate the components in your cluster are FIPS compliant
Synopsis
The check cluster fips command is used to validate that specific components and services are FIPS compliant by checking the signatures of the files against a signed signature file, and checking that services are using the certified algorithms.
Examples:
CODE
To use the built-in signature files for supported operating systems:
dkp check cluster fips
To use a custom signature file, named "manifest-rhel-84.json.asc":
dkp check cluster fips \
--signature-file manifest-rhel-84.json.asc \
--signature-configmap myconfigmap
The file will be copied to the ConfigMap. To use an existing ConfigMap:
dkp check cluster fips \
--signature-configmap myconfigmap
The validation will be re-checked against the existing signature data.
CODE
dkp check cluster fips [flags]
Options
CODE
-h, --help help for fips
--kubeconfig string Path to the kubeconfig file for the fips cluster. If unspecified, default discovery rules apply.
-n, --namespace string If present, the namespace scope for this CLI request. (default "default")
--output-configmap string ConfigMap to store result of the fips check. (default "check-cluster-fips-output") (DEPRECATED: This flag will be removed in a future release.)
--signature-configmap string ConfigMap with fips signature data to verify.
--signature-file string File containing fips signature data.
--timeout duration The length of time to wait before giving up. Zero means wait forever (e.g. 300s, 30m, 3h). (default 10m0s)
Options inherited from parent commands
CODE
-v, --verbose int Output verbosity
SEE ALSO
- dkp check cluster - Check a cluster, one of [fips]