1. Open the kommander.yaml file:

    1. If you do not have the kommander.yaml file, initialize the configuration file, so you can edit it in the following steps. WARNING: Initialize this file only ONCE, otherwise you will overwrite previous customizations.

    2. If you have initialized the configuration file already, open the kommander.yaml with the editor of your choice.

  2. You can use other issuers that support the ACME protocol by configuring the issuer’s server in the installation configuration, for example:

    acme:
      email: <your_email>
      server: <your_server>
    [...]
    CODE
  3. Create a DNS record and install Kommander:

    1. You can set up an external-dns service. This way, the external-dns will take care of pointing the DNS record to the ingress of the cluster automatically.
      In this case: FIRST, set up the external-dns in the kommander.yaml. THEN use the configuration file to install Kommander.

    2. Alternatively, create a DNS record manually, that maps your domain name or IP address to the cluster ingress.
      In this case: FIRST, use the configuration file to install Kommander and wait for the load balancer address to be provisioned. THEN manually create the DNS record pointing to the load balancer address.

Some certificate authorities require setting additional fields for the custom configuration to work. Use the kubectl -n <namespace> patch command to configure any other additional fields in the Issuer or ClusterIssuer. For an example, refer to the ZeroSSL configuration.

Next Topic:

Advanced Configuration of Custom Certificates via ClusterIssuer