ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
The kubectl command-line tool supports several different ways to create and manage Kubernetes objects . This document provides an overview of the different approaches. Read the Kubectl book for details of managing objects by Kubectl. Management techniques Warning: A Kubernetes object should be manag
Started · 01 Sept 2025, 19:44 UTC
Feature state: Stable since Kubernetes v1.24 When you run a Pod on a Node, the Pod itself takes an amount of system resources. These resources are additional to the resources needed to run the container(s) inside the Pod. In Kubernetes, Pod Overhead is a way to account for the resources consumed by
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
Wanted your guidance on an issue while executing a Kubernetes YAML file. My kubectl version is as follows: Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"} Server
Feature state: Stable since Kubernetes v1.20 This page describes the RuntimeClass resource and runtime selection mechanism. RuntimeClass is a feature for selecting the container runtime configuration. The container runtime configuration is used to run a Pod's containers. Motivation You can set a dif
I started using Lens and noticed that it gives you some warnings when the pods inside the nodes have limits higher than the actual capacity. So I tried to get this information with kubectl but I'm new to jsonpath and I just managed to get the raw info using something like this: kubectl get pods -o=jsonpath='{.items..resources.limits}' -A That produces someth
After upgrading to v1.24.0 (after Dockershim removal), I had to install cri-dockerd , then I did the following: sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket=unix:///var/run/cri-dockerd.sock --apiserver-advertise-address=192.168.0.196 I have chosen flannel as Network Plugin: kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/
I have a problem with helm deployment. It has happend after I have added a new environment variable to the deployment. When I execute: helm upgrade [RELEASE] [CHART] I get the following error: Error: The order in patch list: [ map[name:APP_ENV value:prod] map[name:MAILER_URL value:...] map[name:APP_VERSION value:v0-0-3] map[name:APP_COMMIT_SHA value:...] ] d
I'm running a fairly resource-intensive service on a Kubernetes cluster to support CI activities. Only a single replica is needed, but it uses a lot of resources (16 cpu), and it's only needed during work hours generally (weekdays, 8am-6pm roughly). My cluster runs in a cloud and is setup with instance autoscaling, so if this service is scaled to zero, that