TLS <strong>certificate</strong>s for DataVolume imports - Virtual machines | Container-native virtualization

This is a cache of https://docs.openshift.com/container-platform/4.3/cnv/cnv_virtual_machines/cnv_importing_vms/cnv-tls-certificates-for-dv-imports.html. It is a snapshot of the page at 2024-11-23T02:17:22.038+0000.

TLS <strong>certificate</strong>s for DataVolume imports - Virtual machines | Container-native virtualization | OpenShift Container Platform 4.3

Adding TLS certificates for authenticating DataVolume imports
Example: ConfigMap created from a TLS certificate

Adding TLS certificates for authenticating DataVolume imports

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

Create the ConfigMap by referencing the relative file path for the TLS certificate.

Procedure

Ensure you are in the correct namespace. The ConfigMap can only be referenced by DataVolumes if it is in the same namespace.
```
$ oc get ns
```

Create the ConfigMap:

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

Example: ConfigMap created from a TLS certificate

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

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

TLS certificates for DataVolume imports

Adding TLS certificates for authenticating DataVolume imports

Example: ConfigMap created from a TLS certificate