Skip to main content
Version: 1.0.0

Kubernetes Troubleshooting Guide

Deploy Failing

Is your Project stuck in the "Container Crashing" or "Deploy Failed" state and you can't figure out why? This troubleshooting guide goes over tips to debug this issue using K8s Lens. This guide will be applicable to you as long as you are using a cluster on Zeet, regardless of provider (AWS, GCP, DO, Coreweave, etc.).

1. Introducing Lens

Kubernetes Lens is an effective, open-source IDE for Kubernetes. Lens helps you manage and monitor your clusters in real time. Lens is a standalone application that can be installed on MacOS, Windows, and most Linux distros. This guide covers how you can install and set up Lens to debug your Resources.

2. Download Lens

Download and install the Lens Desktop app from the official website.

Once installed, you will be prompted to create a free account or upgrade to Lens Pro. After creating an account and logging in, yous should see a screen that looksl like this.

3. Locate Target cluster

The next step is to find which cluster your Project is running on. You can find this information under the Resources & Replication section in Project Settings. In this case, you should see that the target cluster is the demo-aws cluster.

4. Download Kubeconfig for cluster

From the Settings page, either click on the target cluster (demo-aws in this case) or navigate to the Zeet Cluster Management console (at{team-name}/console/clusters/manage) from the Clusters tab on the vertical nav. From the Cluster Manage console, locate the target cluster of interest, and download kubeconfig from cluster settings.

5. Add cluster in Lens

Back in Lens, now open up the Lens Catalog - this should be the first item in the quick-access Hotbar on the left. Lens should have automatically scanned your OS to show you all kubeconfig files on your system.

If you don't see your cluster here, you can manually add a cluster by navigating to File -> Add Cluster.

Now that Lens has detected your cluster, it's time to open up and connect to the cluster. From the Catalog page, now open up your cluster. You should see a page like this. If you are seeing a message saying, "Metrics are not available due to missing or invalid Prometheus configuration." - this is because you don't have a pod in your cluster that is running Prometheus.

You can now start poking around your cluster to see the health and status of your Pods!