TLS certificates for data volume imports
- Adding TLS certificates for authenticating data volume imports
- Example: Config map created from a TLS certificate

TLS certificates for data volume imports

Adding TLS certificates for authenticating data volume imports

TLS certificates for registry or HTTPS endpoints must be added to a config map to import data from these sources. This config map must be present in the namespace of the destination data volume.

Create the config map by referencing the relative file path for the TLS certificate.

Procedure

Ensure you are in the correct namespace. The config map can only be referenced by data volumes if it is in the same namespace.
```
$ oc get ns
```

Create the config map:

$ oc create configmap <configmap-name> --from-file=</path/to/file/ca.pem>

Example: Config map created from a TLS certificate

The following example is of a config map created from ca.pem TLS certificate.

apiVersion: v1
kind: ConfigMap
metadata:
  name: tls-certs
data:
  ca.pem: |
    -----BEGIN CERTIFICATE-----
    ... <base64 encoded cert> ...
    -----END CERTIFICATE-----