Stack Diagnosis Tools – Comprehensive Troubleshooting & Solutions

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.

OpenShift A route has an invalid configuration, preventing it from being admitted.

The route configuration may have incorrect hostnames, paths, or other parameters.

OpenShift PodNotFound

A specified pod cannot be found, possibly due to deletion or incorrect naming.

OpenShift ServicePortConflict

Two services are configured to use the same port, causing a conflict.

OpenShift InvalidResourceLimit

A resource limit is set incorrectly, causing scheduling or runtime issues.

OpenShift ClusterOperatorDegraded

A cluster operator is in a degraded state, affecting cluster functionality.

OpenShift PodTerminated

A pod was unexpectedly terminated, possibly due to node issues or resource constraints.

OpenShift A pod has an invalid volume mount configuration.

The volume mount paths are incorrectly configured or inaccessible.

OpenShift PodFailedToStart

A pod failed to start due to configuration errors or missing dependencies.

OpenShift Pod fails to start due to missing or incorrect Secret reference.

A pod references a non-existent or incorrectly named Secret.

OpenShift Pods fail to start or exhibit unexpected behavior due to missing or misconfigured ConfigMaps.

A pod references a non-existent or incorrectly named ConfigMap.

OpenShift PodIPConflict

Two pods have been assigned the same IP address, causing network conflicts.

OpenShift ServiceSelectorMismatch

A service selector does not match any pods, preventing traffic routing.

OpenShift Pod stuck in terminating state

Finalizers or resource cleanup issues

OpenShift NodeNetworkUnavailable

A node's network is unavailable, affecting pod communication and scheduling.

OpenShift A pod or container fails to start due to invalid resource requests or limits.

The resource requests or limits specified for a pod or container are outside the allowable range or incorrectly formatted.

OpenShift PodSecurityContextViolation

A pod's security context violates security policies, preventing it from being scheduled.

OpenShift PodDisruptionBudgetViolation

A pod disruption budget is violated, preventing voluntary disruptions.

OpenShift NodeUnschedulable

A node is marked as unschedulable, preventing new pods from being scheduled.

OpenShift Pod anti-affinity rules cannot be satisfied, preventing pod scheduling.

Pod anti-affinity rules are too restrictive, or there are insufficient resources or nodes to satisfy the rules.

OpenShift CrashLoopBackOff

The container repeatedly fails to start due to an application error or misconfiguration.

OpenShift ServiceLoadBalancerPending

A LoadBalancer service is pending due to cloud provider issues or misconfiguration.

OpenShift DeploymentConfigNotProgressing

A deployment is not progressing due to errors or resource constraints.

OpenShift PodAffinityRulesNotSatisfied

Pod affinity rules cannot be satisfied, preventing pod scheduling.

OpenShift Build process fails in OpenShift.

Errors in the build configuration or source code.

OpenShift NodePIDPressure

A node is experiencing PID pressure, affecting pod scheduling and performance.

OpenShift IngressNotConfigured

Ingress resources are not properly configured, preventing external access.

OpenShift NodeMemoryPressure

A node is experiencing memory pressure, affecting pod scheduling and performance.

OpenShift NodeDiskPressure

A node is experiencing disk pressure, affecting pod scheduling and performance.

OpenShift Authentication failures due to expired service account token.

A service account token has expired.

OpenShift PodSecurityPolicyViolation

A pod violates the security policies in place, preventing it from being scheduled.

OpenShift PersistentVolumeClaim is bound to an incorrect PersistentVolume.

A PersistentVolumeClaim is bound to an incorrect PersistentVolume.

OpenShift Route not admitted due to conflicting hostnames or misconfiguration.

A route is not admitted because of conflicting hostnames or incorrect configuration.

OpenShift The Horizontal Pod Autoscaler (HPA) is unable to scale the application pods as expected.

The HPA cannot scale due to missing metrics or configuration issues.

OpenShift LivenessProbeFailed

The liveness probe for a container is failing, causing the container to be restarted.

OpenShift DNSResolutionFailed

DNS queries are failing, possibly due to misconfigured DNS settings.

OpenShift ReadinessProbeFailed

The readiness probe for a container is failing, indicating the application is not ready to serve traffic.

OpenShift Invalid image name error encountered during deployment.

The specified image name does not adhere to the required format.

OpenShift Resource quota limits have been exceeded for a project or namespace.

Resource quota limits have been exceeded for a project or namespace.

OpenShift Network policies are preventing traffic to or from a pod.

Network policies are configured in a way that blocks necessary traffic.

OpenShift PersistentVolumeClaimPending

A PersistentVolumeClaim cannot be bound to a PersistentVolume.

OpenShift CertificateExpired

A TLS certificate used by a service or route has expired.

OpenShift PodEvicted

A pod was evicted due to resource pressure on the node.

OpenShift ServiceUnavailable

A service is not reachable, possibly due to network issues or misconfiguration.

OpenShift Unauthorized

Access to a resource is denied due to invalid credentials or permissions.

OpenShift OOMKilled

The container was terminated because it exceeded its memory limit.

OpenShift FailedScheduling

The scheduler cannot place a pod due to resource constraints or affinity rules.

OpenShift NodeNotReady

A node is not in a ready state, possibly due to network issues or resource exhaustion.

OpenShift Pending Pods

Pods are unable to be scheduled due to insufficient resources or constraints.

OpenShift ErrImagePull

The image cannot be pulled due to incorrect credentials or image not found.

OpenShift ImagePullBackOff

The container runtime is unable to pull the specified image from the registry.

Rancher Failed to Configure RBAC

Misconfigured role bindings or insufficient permissions.

Rancher Failed to Update Resource

Resource conflicts or insufficient permissions.