Overview

If you deploy your Konvoy cluster with custom domain name and certs (as documented ) and you are still using ArgoCD and it's UI as installed by the Dispatch component, then may experience a problem with accessing the ArgoCD UI.   This is because the ArgoCD component is not automatically reconfigured with the new cluster certificate.

Solution

To remedy this issue, you must be using Dispatch 1.4.2.  This version of Dispatch includes a new option that enables you to set a custom security certificate in the ArgoCD UI component.   

To use this new option, you need to duplicate your custom cert secret into the dispatch namespace, and then update the dispatch section of your cluster.yaml as follows (assuming the secret name is custom-cert):

    - configRepository: https://github.com/mesosphere/kubeaddons-dispatch
      configVersion: stable-1.19-1.4.2
      addonsList:
        - name: dispatch
          enabled: true
          values: |
            dispatch:
              clusterHostname: 
            argo-cd:
              enabled: true
              konvoyDex:
                enabled: true
              server:
                caSecretName: custom-cert