Skip to main content
Skip table of contents

Log in to the UI with Kommander

By default, you can log in to the UI in Kommander with the credentials given using this command:

dkp open dashboard --kubeconfig=${CLUSTER_NAME}.conf

You can also retrieve your credentials at any time using the following command:

kubectl -n kommander get secret dkp-credentials -o go-template='Username: {{.data.username|base64decode}}{{ "\n"}}Password: {{.data.password|base64decode}}{{ "\n"}}'

You can also retrieve the URL used for accessing the UI using the following command:

kubectl -n kommander get svc kommander-traefik -o go-template='https://{{with index .status.loadBalancer.ingress 0}}{{or .hostname .ip}}{{end}}/dkp/kommander/dashboard{{ "\n"}}'

You should only use these static credentials to access the UI for configuring an external identity provider. Treat them as back up credentials rather than use them for normal access.

You rotate the password using the following command:

dkp experimental rotate dashboard-password

The output displays the new password:

Password: kqZ31lMBSCLcBjUKVwLJMQL2PxalipIzZw5Pjyw09wDqjWV3dz2wPSSBYi09JGJp

You can perform the following operations on Identity Providers:

  • Create an Identity Provider

  • Temporarily Disable an Identity Provider

  • Create Groups

Dashboard UI Functions

After installing Konvoy component and building a cluster as well as successfully installing Kommander and logging into the UI, you are now ready to customize configurations using the Day 2 Cluster Operations Management section of the documentation. The majority of this customization such as attaching clusters and deploying applications will take place in the dashboard or UI of DKP. The Day 2 section allows you to manage cluster operations and their application workloads to optimize your organization’s productivity.

See DKP Insights if you want to enable a solution that detects current and future anomalies in workload configurations or Kubernetes clusters.

Next Step

Day 2 - Cluster Operations Management

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.