If you want to ensure the customization for a domain and certificate is completed, or if you want to obtain more information on the status of the customization, display the status information for the KommanderCluster.

  1. Inspect the modified KommanderCluster object:

    kubectl describe kommandercluster -n <workspace_name> <cluster_name>
    CODE
  2. If the ingress is still being provisioned, the output looks similar to this:

    [...]
    Conditions:
      Last Transition Time:  2022-06-24T07:48:31Z
      Message:               Ingress service object was not found in the cluster
      Reason:                IngressServiceNotFound
      Status:                False
      Type:                  IngressAddressReady
    [...]
    CODE

    If the provisioning has been completed, the output looks similar to this:

    [...]
    Conditions:
      Last Transition Time:  2022-06-28T13:43:33Z
      Message:               Ingress service address has been provisioned
      Reason:                IngressServiceAddressFound
      Status:                True
      Type:                  IngressAddressReady
      Last Transition Time:  2022-06-28T13:42:24Z
      Message:               Certificate is up to date and has not expired
      Reason:                Ready
      Status:                True
      Type:                  IngressCertificateReady
    [...]
    CODE

    The same command also prints the actual customized values for the KommanderCluster.Status.Ingress. Here is an example:

    [...]
       ingress:
        address: 172.20.255.180
        caBundle: LS0tLS1CRUdJTiBD...<output has been shortened>...DQVRFLS0tLS0K
    [...]
    CODE

Related Topics

Why Should you set up a Custom Domain or Certificate?

Configuration Example with Let's Encrypt

Configure Custom Domains or Custom Certificates post Kommander Installation