Skip to main content
Zylon comes with a built-in Kubernetes Dashboard, which will help you monitor and diagnose issues with your installation. To enable it, you will need to edit your config file at /etc/zylon/zylon-conf.yaml and add the following section:
Next, update your Zylon system by running:
Once the update completes, access the dashboard at: https://<zylon.company.com>/kube-dashboard To login, you can generate a short-lived token:
Or a permanent token:
The permanent token will provide full admin access to your Kubernetes cluster. Keep it secret and secure.
Zylon uses multiple namespaces, you can check the status of each. Select the right namespace from the dropdown on the top left corner.
  • zylon: Zylon system components
  • openebs: OpenEBS storage system
  • nvidia: NVIDIA controller and device plugin
After logging in, you will be able to see the status of your Zylon installation, including:
  • Pods
  • Logs
  • Basic metrics regarding CPU and memory usage

​
Frequent Questions

This section explains how to navigate the Kubernetes Dashboard to investigate common issues in your Zylon installation.

​
❓ Where do I start when something is not working?

When you first open the Kubernetes Dashboard, you’ll see a high-level overview of your workloads and cluster health. This view shows the current status of running resources such as Pods, Deployments, and basic CPU/memory usage. image

​
❓ Which namespace should I select?

Zylon uses multiple namespaces, but most workspace and platform issues will be in the zylon namespace.
  1. Open the namespace dropdown in the top-left corner of the dashboard
  2. Select the namespace you want to check
  3. The dashboard will refresh and show only that namespace’s system components
This helps reduce noise and ensures you are inspecting the correct resources. image

​
❓ How do I view logs for a Pod?

To inspect logs for a specific Pod:
  1. Click on the Pod name you want to investigate
  2. This opens the Pod details page with:
  • Status
  • Events
  • Resource usage
  • Containers
  1. In the top-right corner, click Logs image You can:
  • View live logs
  • Download logs for offline analysis if your instance is airgap
Logs are usually the fastest way to identify configuration errors, startup failures, or runtime issues.