If you do not have the
kommander.yamlfile, 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.
If you have initialized the configuration file already, open the
kommander.yamlwith the editor of your choice.
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
Create a DNS record and install Kommander:
You can set up an external-dns service. This way, the
external-dnswill take care of pointing the DNS record to the ingress of the cluster automatically.
In this case: FIRST, set up the
kommander.yaml. THEN use the configuration file to install Kommander.
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
ClusterIssuer. For an example, refer to the ZeroSSL configuration.