ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
This page describes the Kubernetes API kinds that dynamic resource allocation (DRA) uses to categorize, request, and allocate devices. DRA terminology DRA uses the following Kubernetes API kinds to provide the core allocation functionality. All of these API kinds are included in the resource.k8s.io/
Started · 12 Sept 2022, 21:01 UTC
Feature state: Beta since Kubernetes v1.36; enabled by default Kubernetes 1.37 includes a beta feature that lets an API Server proxy resource requests to other peer API servers. It also lets clients get a holistic view of resources served across the entire cluster through discovery. This is useful w
The goal is to understand whether Kubernetes retains container logs for a pod that has exited due to a CrashLoopBackOff event after the pod itself is deleted or evicted. Currently, logs are stored only on the node’s filesystem and are removed according to the node’s log‑rotation policy, with no built‑in API to access them once the pod is gone. This leaves an
In a Kubernetes cluster, a node can be shut down in a planned graceful way or unexpectedly because of reasons such as a power outage or something else external. A node shutdown could lead to workload failure if the node is not drained before the shutdown. A node shutdown can be either graceful or no
Understand how to gain end-to-end visibility of a Kubernetes cluster through the collection of metrics, logs, and traces. In Kubernetes, observability is the process of collecting and analyzing metrics, logs, and traces—often referred to as the three pillars of observability—in order to obtain a bet
Goal: Determine whether Helm v3 can reduce latency spikes observed when multiple helm install or helm upgrade commands run concurrently without relying on external serialization. Constraints/uncertainty: The observed latency stems from Kubernetes API server queuing, etcd lock contention, and overlapping exponential backoff retries; it is unclear if adding a
Feature state: Beta since Kubernetes v1.37; disabled by default More information about this feature To use this feature, you (or a cluster administrator) will need to enable the PodLevelResourceManagers feature gate for all relevant components in your cluster. See Enable Or Disable Feature Gates for
This page describes how to observe the status and health of resources that are dynamically allocated with DRA. Observability of dynamic resources You can check the status of dynamically allocated resources by using any of the following methods: kubelet device metrics ResourceClaim status Device heal
Feature state: Stable since Kubernetes v1.20 Kubernetes allow you to limit the number of process IDs (PIDs) that a Pod can use. You can also reserve a number of allocatable PIDs for each node for use by the operating system and daemons (rather than by Pods). Process IDs (PIDs) are a fundamental reso
helm