Giving Kubernetes Superpowers to everyone
Go to file
2023-03-21 22:05:34 +00:00
.github/workflows updated workflows 2023-03-21 21:47:20 +00:00
cmd restructure 2023-03-21 21:00:18 +00:00
images updated copy 2023-03-21 20:36:45 +00:00
pkg first 2023-03-21 21:23:59 +00:00
.gitignore adding workflow 2023-03-21 20:09:18 +00:00
.goreleaser.yaml adding workflow 2023-03-21 20:09:18 +00:00
CONTRIBUTING.md Rename CONTRIBUTING to CONTRIBUTING.md 2023-03-21 22:05:01 +00:00
go.mod adding workflow 2023-03-21 20:09:18 +00:00
go.sum updated copy on readme 2023-03-21 19:58:32 +00:00
LICENSE Update LICENSE 2023-03-21 22:01:53 +00:00
main.go first 2023-03-21 11:56:05 +00:00
README.md Update README.md 2023-03-21 22:05:34 +00:00

k8sgpt


AI Powered Kubernetes debugging for SRE, Platform and DevOps teams.

What is k8sgpt?

k8sgpt is a tool for scanning your kubernetes clusters, diagnosing and triaging issues in simple english.

It reduces the mystery of kubernetes and makes it easy to understand what is going on in your cluster.

Usage

# Ensure KUBECONFIG env is set to an active Kubernetes cluster
k8sgpt auth key <Your OpenAI key>

k8sgpt find problems --explain

Configuration

k8sgpt stores config data in ~/.k8sgpt the data is stored in plain text, including your OpenAI key.

Example

 k8sgpt find problems --explain
default/deathstar-5b559d699b-d4jm7: Back-off pulling image "docker.io/cilium/starwaraaes"


The Kubernetes error message: Back-off pulling image "docker.io/cilium/starwaraaes" means that the Kubernetes cluster is having trouble pulling the specified container image from the Docker registry. 

To solve this issue, you can try the following:

1. Check if the specified image exists in the Docker registry by running the following command:

    `docker pull docker.io/cilium/starwaraaes`

2. If the image exists, try pulling the image manually on the node where the container is trying to run. This can be done by running the following command:

    `docker pull docker.io/cilium/starwaraaes`

3. If the image is not found in the Docker registry, check if the image name and tag are correct.

4. If the issue persists, check the Docker engine logs for any error messages that might provide more context on the issue.
placed-application-demo/placed-application-demo-58469d688c-7wdps: 0/5 nodes are available: 5 node(s) were unschedulable. preemption: 0/5 nodes are available: 5 Preemption is not helpful for scheduling..