Debug Your Infrastructure

Get Instant Solutions for Kubernetes, Databases, Docker and more

Quick Fix
Deep Dive
Best Practice
Step-By-Step
Tools
AWS CloudWatch
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Pod Stuck in CrashLoopBackOff
Database connection timeout
Docker Container won't Start
Kubernetes ingress not working
Redis connection refused
CI/CD pipeline failing

K3s NodeNotFound

A specified node cannot be found, possibly due to incorrect node name or deletion.

Understanding K3s and Its Purpose

K3s is a lightweight Kubernetes distribution designed for resource-constrained environments and edge computing. It simplifies the deployment and management of Kubernetes clusters, making it an ideal choice for IoT and CI/CD environments. For more information, you can visit the official K3s website.

Identifying the NodeNotFound Symptom

When working with K3s, you might encounter the NodeNotFound error. This issue typically manifests when a specified node cannot be found within the cluster. You may notice this error in the logs or when running commands that interact with nodes.

Common Observations

  • Error messages indicating a node is missing.
  • Inability to schedule workloads on the missing node.
  • Discrepancies in the node list when using kubectl get nodes.

Explaining the NodeNotFound Issue

The NodeNotFound error occurs when a node is not recognized by the K3s cluster. This can happen due to several reasons, such as:

  • Incorrect node name specified in commands or configurations.
  • The node has been removed or is no longer part of the cluster.
  • Network issues preventing the node from communicating with the cluster.

Understanding the root cause is crucial for resolving the issue effectively.

Steps to Fix the NodeNotFound Issue

Follow these steps to diagnose and resolve the NodeNotFound error:

1. Verify Node Name

Ensure that the node name you are using is correct. You can list all nodes in the cluster using:

kubectl get nodes

Check the output to confirm the node's name and status.

2. Check Node Registration

If the node is not listed, it may not be registered with the cluster. Re-register the node by restarting the K3s agent on the node:

sudo systemctl restart k3s-agent

After restarting, verify the node's presence again using kubectl get nodes.

3. Investigate Network Issues

Network connectivity issues can prevent a node from communicating with the cluster. Check the network configuration and ensure that the node can reach the server:

ping <server-ip>

Resolve any network issues that may be affecting connectivity.

Additional Resources

For further assistance, consider exploring the following resources:

These resources provide comprehensive information and community support for troubleshooting K3s-related issues.

Master 

K3s

 debugging in Minutes

— Grab the Ultimate Cheatsheet

(Perfect for DevOps & SREs)

Most-used commands
Real-world configs/examples
Handy troubleshooting shortcuts
Your email is safe with us. No spam, ever.

Thankyou for your submission

We have sent the cheatsheet on your email!
Oops! Something went wrong while submitting the form.

K3s

Cheatsheet

(Perfect for DevOps & SREs)

Most-used commands
Your email is safe thing.

Thankyou for your submission

We have sent the cheatsheet on your email!
Oops! Something went wrong while submitting the form.

MORE ISSUES

K3s PodFailedToWatch
A pod failed to watch, possibly due to misconfiguration or resource issues.
K3s PodFailedToWrite
A pod failed to write, possibly due to misconfiguration or resource issues.
K3s PodFailedToWait
A pod failed to wait, possibly due to misconfiguration or resource issues.
K3s PodFailedToVerify
A pod failed to verify, possibly due to misconfiguration or resource issues.
K3s PodFailedToValidate
A pod failed to validate, possibly due to misconfiguration or resource issues.
K3s PodFailedToUpdate
A pod failed to update, possibly due to misconfiguration or resource issues.
K3s PodFailedToAttachVolume
A pod failed to attach a volume, possibly due to incorrect volume configuration.
K3s PodFailedToStop
A pod failed to stop, possibly due to finalizers or resource cleanup issues.
K3s PodFailedToStartContainer
A pod failed to start a container, possibly due to misconfiguration or resource issues.
K3s PodFailedToPullImage
A pod failed to pull an image, possibly due to incorrect image name or lack of access.
K3s PodFailedToSchedule
A pod failed to schedule due to constraints or lack of resources.
K3s PodFailedToMountVolume
A pod failed to mount a volume, possibly due to incorrect volume configuration.
K3s NodeNotReadyDueToDiskPressure
A node is not ready due to disk pressure, affecting pod scheduling.
K3s PodFailedToStart
A pod failed to start due to misconfiguration or resource issues.
K3s PodFailedToCreate
A pod failed to create due to misconfiguration or resource issues.
K3s PodFailedToDelete
A pod failed to delete, possibly due to finalizers or resource cleanup issues.
K3s NodeNotRegistered
A node is not registered with the cluster, affecting pod scheduling.
K3s PodSecurityContextViolation
A pod violates security context constraints, preventing it from running.
K3s PodOOMKilled
A pod was killed due to out-of-memory conditions.
K3s PodLivenessProbeFailure
A pod's liveness probe is failing, causing the pod to be restarted.
K3s PodAffinityRulesNotSatisfied
Pod affinity or anti-affinity rules are not satisfied, preventing scheduling.
K3s PodReadinessProbeFailure
A pod's readiness probe is failing, affecting service availability.
K3s PodInitContainerFailure
An init container in a pod has failed, preventing the pod from starting.
K3s Pods are not being scheduled on a node due to a taint.
A node taint is preventing pod scheduling.
K3s Ingress resources are not accessible.
Ingress resources are not accessible, possibly due to misconfiguration.
K3s Service account token has expired, affecting pod authentication.
A service account token has expired.
K3s Pod cannot pull an image due to missing or incorrect image pull secret.
A pod is unable to access the required image because the image pull secret is either missing or incorrectly configured.
K3s PodSecurityPolicyViolation
A pod violates a PodSecurityPolicy, preventing it from being scheduled.
K3s Network policies are blocking traffic, affecting pod communication.
Network policies are blocking traffic, affecting pod communication.
K3s Kubelet service is not running on a node, affecting pod management.
The kubelet service is not running on a node.
K3s Pod stuck in terminating state
A pod is stuck in terminating state, possibly due to finalizers or resource cleanup issues.
K3s NodeOutOfDisk
A node has run out of disk space, affecting pod scheduling and operation.
K3s UnauthorizedAccess
Access is denied due to incorrect credentials or permissions.
K3s API requests are timing out
Network issues or high load on the API server
K3s PersistentVolumeClaimPending
A PersistentVolumeClaim is pending due to lack of available PersistentVolumes.
K3s Network is unavailable on a node, affecting pod communication.
Network configuration issues or connectivity problems.
K3s NodeNotFound
A specified node cannot be found, possibly due to incorrect node name or deletion.
K3s FailedScheduling
A pod cannot be scheduled due to constraints or lack of resources.
K3s High memory usage observed in K3s cluster.
Excessive memory usage by pods or system components, causing resource exhaustion.
K3s NodeDiskPressure
A node is experiencing disk pressure, leading to pod eviction or scheduling issues.
K3s FailedMount
A pod cannot mount a volume, possibly due to incorrect volume configuration.
K3s Pods are unable to resolve DNS names.
CoreDNS issues causing DNS resolution failure.
K3s Pods are being evicted unexpectedly.
Pods are evicted due to resource constraints or node pressure.
K3s High CPU Usage
Excessive CPU usage by pods or system components, leading to performance degradation.
K3s PodUnschedulable
A pod cannot be scheduled due to insufficient resources or node constraints.
K3s ImagePullBackOff
K3s is unable to pull the specified container image, possibly due to incorrect image name or lack of access.
K3s Communication failures between K3s components due to expired certificates.
K3s certificates have expired, causing communication failures between components.
K3s ServiceUnavailable
A service is not reachable, possibly due to misconfigured service or network policies.
K3s NodeNotReady
The node is not in a ready state, possibly due to network issues or resource constraints.
K3s CrashLoopBackOff
A pod is repeatedly crashing due to application errors or misconfiguration.

Backed by

Resources

DocumentationFun For DevsBlog

Contact

Contact UsAbout UsCareersTerms and ConditionsPrivacy PolicyShipping & and Delivery PolicyCancellation & Refund Policy

Platform

AI OpsAlert Grouping & De-DuplicationPlayBooksKubernetes Bot

Connect

Slack CommunityGithubLinkedInX (Twitter)
Deep Sea Tech Inc. — Made with ❤️ in Bangalore & San Francisco 🏢

Doctor Droid