Кубернетичек

We worked with Bayer Crop Science to create Google Kubernetes Engine clusters with up to 15,000 nodes.

What happened? Except for the case when the privileged field is enabled in a container securityContext, cgroup fs is mounted in /sys/fs/cgroup as read only. While this behavior is desirable for mos...

Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon Europe in Paris from March 19-22, 2024. Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at

The Kubernetes Storage Layer: Peeling the Onion Minus the Tears - Madhav Jivrajani, VMware The Kuberentes storage layer to the end user is etcd, but it actually consists of 3 different layers. In order to scale Kubernetes to the limits it can today, a significant amount of work has been done and continues to happen on the storage layet. The 3 layers of abstraction are - the watch cache, the cacher and finally etcd. Understanding how API requests interact with each layer can have significant cost reductions and performance gains, and understanding the implementation of these layers can seem challenging, but it doesn't have to be! Knowing the internals of the storage layer can greatly supplement a user's existing knowledge of their workloads and can help them starting from capacity planning all the way to writing better controllers. A rough outline of the talk is as follows: - Overview of how Kubernetes processes requests - The Cacher - The watch cache - Potential CPU and Memory hotspots at each layer - Recent work done to improve reliability and scalability - Q&A

This is the second blog post about the sched_ext, a BPF-based extensible scheduler class. In this blog post, I briefly update what has been happening in sched_ext, then introduce the scheduler architecture and the sched_ext API. After reading this, you should have a good understanding of the sched_ext architecture and be ready to read the source code of any sched_ext schedulers.

Kubernetes reserves all labels and annotations in the kubernetes.io and k8s.io namespaces. This document serves both as a reference to the values and as a coordination point for assigning values. Labels, annotations and taints used on API objects apf.kubernetes.io/autoupdate-spec Type: Annotation Example: apf.kubernetes.io/autoupdate-spec: "true" Used on: FlowSchema and PriorityLevelConfiguration Objects If this annotation is set to true on a FlowSchema or PriorityLevelConfiguration, the spec for that object is managed by the kube-apiserver.

One-Click: Deploy your favourite container with a single click in Kubernetes. - janlauber/one-click

One-line PR description: Update the DRA API and design for Kubernetes 1.31 Issue links: DRA: structured parameters #4381 DRA: control plane controller ("classic DRA") #3063 ...

Kubernetes components use on-off switches called feature gates to manage the risk of adding a new feature. The feature gate mechanism is what enables incremental graduation of a feature through the stages Alpha, Beta, and GA. Kubernetes components, such as kube-controller-manager and kube-scheduler, use the client-go library to interact with the API. The same library is used across the Kubernetes ecosystem to build controllers, tools, webhooks, and more. client-go now includes its own feature gating mechanism, giving developers and cluster administrators more control over how they adopt client features.