In DKP 2.4, a new feature to wait until the installation of applications had been introduced in order to ensure that all applications are ready before the operator attempts to access the ops portal.
Problem
In the event that despite waiting for several minutes (30+), the deployment of Kommander looks to be stuck such as shown below, you may be able to check the status of the Helm Release deployments and troubleshoot exactly where it fails.
$ ./dkp install kommander --installer-config ./kommander_minimal.yaml --kubeconfig=${CLUSTER_NAME}.conf
✓ Running pre-flight checks
✓ Fetching applications repository
✓ Deploying base resources
✓ Deploying Flux
✓ Deploying Kommander root CA
✓ Deploying ChartMuseum
✓ Deploying Helm repositories
✓ Deploying Ingress certificate
✓ Deploying Gitea
✓ Pushing application definitions to Gitea
✓ Bootstrapping management Git repository
✓ Deploying age encryption secret
✓ Deploying Flux configuration
✓ Deploying Gatekeeper
✓ Deploying Kommander AppManagement
✓ Deploying core AppDeployments
✓ Deploying AppDeployments for enabled applications
✓ Deploying configured catalog repositories
⠈⠑ Waiting for 9 enabled applications to be ready [========================> 6/9] (time elapsed 15m18s)
Solution
In another console window, using your cluster configuration file, check the status of the Helm Release deployment:
$ kubectl get hr -A --kubeconfig=${CLUSTER_NAME}.conf
NAMESPACE NAME AGE READY STATUS
kommander-default-workspace karma-traefik-certs 6m19s True Release reconciliation succeeded
kommander-default-workspace kubecost-traefik-certs 6m19s True Release reconciliation succeeded
kommander-default-workspace prometheus-traefik-certs 6m19s True Release reconciliation succeeded
kommander cluster-observer-2360587938 5m1s True Release reconciliation succeeded
kommander dex 11m True Release reconciliation succeeded
kommander dex-k8s-authenticator 11m False dependency 'kommander/traefik' is not ready
kommander gatekeeper 14m True Release reconciliation succeeded
kommander gatekeeper-proxy-mutations 14m True Release reconciliation succeeded
kommander gitea 16m True Release reconciliation succeeded
kommander karma-traefik-certs 6m19s True Release reconciliation succeeded
kommander kommander 10m True Release reconciliation succeeded
kommander kommander-appmanagement 13m True Release reconciliation succeeded
kommander kubecost-traefik-certs 6m19s True Release reconciliation succeeded
kommander kubefed 9m32s True Release reconciliation succeeded
kommander prometheus-traefik-certs 6m19s True Release reconciliation succeeded
kommander reloader 10m True Release reconciliation succeeded
kommander traefik 10m False Helm install failed: timed out waiting for the condition
kommander traefik-forward-auth-mgmt 9m49s False dependency 'kommander/traefik' is not ready
From here you can drill down further by doing a kubectl describe hr for the affected Helm Release or to do a kubectl get logs on pods that are failing to start.