Comments (1)
brandond
commented on June 24, 2024
Kubernetes cannot reason about pods on nodes that do not have a running kubelet. You may have deleted the pod, but Kubernetes does not actually know if it is terminated or not because the kubelet is not running to provide status updates. It may actually be running on a node suffering a network outage, it may be running but the Kubelet is stopped, it might not be running at all. Kubernetes has no way of knowing.
There will be no updates to the pod status until the node either comes back online, or the node is deleted and the pod is force-deleted as an orphan.
This is not a K3s issue, this is just how Kubernetes works. There are some discussions about tuning the apiserver and controller-manager to reduce internal node monitor intervals, which may aid in evicting pods from offline nodes, at #1264 (comment)
from k3s.
Related Issues (20)
- Duplicate mirror endpoint causes containerd to fail to load mirror config from hosts.toml HOT 2
- [Release-1.28] - Duplicate mirror endpoint causes containerd to fail to load mirror config from hosts.toml HOT 1
- [Release-1.27] - Duplicate mirror endpoint causes containerd to fail to load mirror config from hosts.toml
- [Release-1.26] - Duplicate mirror endpoint causes containerd to fail to load mirror config from hosts.toml HOT 1
- Single-node k3s etcd failed to reconcile HOT 3
- How to set default runtime (for example, nvidia) for k3s? HOT 1
- k3s etcd restore fails on host with IPv6 only HOT 2
- Integrate k3s and multus
- Failed to pull image: failed to pull and unpack image HOT 1
- Cluster DNS not working HOT 2
- K3S with AWS VPC CNI breaks Pod communication HOT 2
- vCluster HA config Issue HOT 1
- k3s will listen on random ports
- Both Endpoints and EndpointSlices not working with Service abstraction for external IPs
- containerd does not fall back to default endpoint when using wildcard registry entry HOT 1
- [Release-1.28] - containerd does not fall back to default endpoint when using wildcard registry entry HOT 1
- [Release-1.27] - containerd does not fall back to default endpoint when using wildcard registry entry HOT 1
- [Release-1.26] - containerd does not fall back to default endpoint when using wildcard registry entry HOT 1
- k3s cadvisor lacks container metrics when i use crid-docker and prometheus operator HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from k3s.