Skip to main content
Remote Console access to virtual machines (VMs) is not available through the Edge Infrastructure Services interface for EVE-k (the EVE-OS variant for Kubernetes) 16.0 LTS clusters. Virtual Network Computing (VNC) provides a workaround for accessing VM consoles running on EVE-k nodes. This procedure uses kubectl, virtctl, and EdgeView. The kubectl and virtctl permissions available through this path are read-only: you can get and list resources but cannot apply or delete them.

Prerequisites

Before starting, confirm the following:
  • kubectl is installed on your workstation.
  • virtctl is installed on your workstation.
  • EdgeView access is enabled for the node running the VM.
  • A Virtual Machine Instance (VMI) is running on an EVE-k cluster.

Get the Kubeconfig via EdgeView

Use the EdgeView TCP tunnel to download the kubeconfig for the cluster:
The kubeconfig file downloads to /tmp/download/kube-config.yaml. All subsequent commands in this article use this file.

List Virtual Machine Instances

List the VMIs running in the eve-kube-app namespace to find the name of the target VM:
Note the VMI name from the output. You will use it in the following steps.

Connect to a VM Console

Open a serial console session to the VM:
Replace <vmi-name> with the name from the VMI list.

Start a VNC Session

Open a VNC session to access the VM’s graphical console:
Replace <vmi-name> with the name from the VMI list. This command opens a VNC viewer connected to the VM’s display.

Optional: Set Shell Aliases

To reduce repetition when running multiple commands, set shell aliases for kubectl and virtctl with the kubeconfig pre-configured:
With these aliases set, use the shortened forms:
These aliases apply only to the current shell session. Add them to your shell profile to make them persistent.

Next Steps

Create and Manage a Kubernetes Cluster

Provision and configure ZEDEDA Edge Kubernetes Service clusters.

Troubleshoot Edge Kubernetes

Diagnose cluster and pod issues using kubectl, EdgeView, and SSH.