Skip to main content
This article covers diagnostic techniques for ZEDEDA Edge Kubernetes Service clusters. Use the Cluster Shell for quick in-browser access, or connect directly using a downloaded kubeconfig, EdgeView, or SSH for deeper troubleshooting.

​
Access the Cluster Shell

The Cluster Shell provides an in-browser kubectl session connected directly to your cluster. No local tooling is required. To open the Cluster Shell:
  1. Navigate to the cluster detail page.
  2. Select Cluster Shell in the page header.
A terminal session opens in the browser. You can run kubectl commands immediately.

​
Common kubectl Diagnostics

​
Check node status

Verify that all nodes are registered and in the Ready state:
The -o wide flag shows additional columns including the node’s IP address and the operating system image.

​
List all pods

List pods across all namespaces to identify failed or pending workloads:

​
Describe a pod

Get detailed information about a specific pod including events, resource requests, and container state:
Replace <namespace> and <pod-name> with the target values from the pod list.

​
View pod logs

Stream live logs from a running container:
The -f flag follows the log stream. Omit it to retrieve existing log output only.

​
View fleet agent logs (GitOps troubleshooting)

The GitOps fleet agent in ZEDEDA Edge Kubernetes Service runs in the zks-fleet-system namespace, not in the default Rancher Fleet namespace. To view agent logs:
These logs show repository polling activity, bundle application results, and any errors reported by the fleet agent.

​
Collect full diagnostics

For comprehensive diagnostic output from a node, run the collect-info.sh script directly on the node. Run it on each node where issues are observed. Share the output when contacting ZEDEDA support.

​
Access a Cluster Without the Cluster Shell

​
Download kubeconfig

To use kubectl from your local workstation:
  1. On the cluster detail page, open the header action dropdown.
  2. Select Download Kubeconfig.
  3. Save the file to your workstation.
Use the downloaded file with any kubectl command:

​
Access via EdgeView

Use the EdgeView TCP tunnel to retrieve the kubeconfig without navigating the Edge Infrastructure Services interface:
The kubeconfig file downloads to /tmp/download/kube-config.yaml. Use it with kubectl as shown in the previous section.

​
Access via SSH

To open a shell directly on the cluster from an SSH session to the node, run:
This drops you into a shell with cluster access on the node.

​
Common Pod Status Reference

​
Common Cluster Status Reference

The following states appear during cluster provisioning and initialization:

​
Next Steps

Create and Manage a Kubernetes Cluster

Provision and configure ZEDEDA Edge Kubernetes Service clusters.

Create GitOps Repositories

Set up automated app delivery from a Git repository.

VNC for EVE-k Apps

Access VM consoles on EVE-k clusters using VNC and virtctl.