DE 

//Cloudogu EcoSystem Docs

  1. docs.cloudogu.com
  2. User manual
  3. Automatic Migration
  4. How-To Guides
  5. Using custom TLS CAs
Getting Started
User manual
Developer documentation

Using custom TLS CAs

The importer offers the option of using your own TLS CAs to verify the exporting server or the mail server.

Provinding CAs for the exporting server

CAs must be provided to the importer via a config map. The name of the config map must be ces-importer-exporter-ca. The key for your own CAs must be named exporter.crt. It can be created with the following command:

kubectl create configmap ces-importer-exporter-ca --from-file=exporter.crt=<Pfad/zur/CA/Datei> --namespace=ecosystem

The importer has to be restarted for the changes to take effect.

The name and key in the ConfigMap can be customized via values.yaml (see).

Provinding CAs for the mail server

CAs must be provided to the importer via a config map. The name of the config map must be ces-importer-mail-ca. The key for your own CAs must be named mail.crt. It can be created with the following command:

kubectl create configmap ces-importer-mail-ca --from-file=mail.crt=<Pfad/zur/CA/Datei> --namespace=ecosystem

The importer has to be restarted for the changes to take effect.

The name and key in the ConfigMap can be customized via values.yaml (see).