-
Looking back: a tour of blog posts » Giant Swarm
We’re embarking on an expedition through the archives of Giant Swarm’s blog. We’re dusting off our virtual time machines and donning our trusty Sherlock hats (aka looking at old links 😀) to decode the mysteries hidden within our old blog posts. But hold on, this isn’t a mere nostalgia trip; we’re on a quest to…
-
Cloud native predictions for 2024 » Giant Swarm
Hard to fathom we’re already a month into 2024! With the new year comes speculation about what’s on the horizon. Peeking around the corner at what’s next is one of my favorite pastimes. But before gazing farther ahead, it’s worth glancing back… In retrospect, 2023 was a transformative year. We connected IRL at KubeCon, VMware…
-
Maximizing value with Kubernetes-as-a-Product: fulfilling the promise of the cloud » Giant Swarm
The cloud and DevOps promised to make our infrastructure faster, cheaper and easier. However, in many organizations, this promise, unfortunately, fell short. Engineering teams find themselves trapped in a cycle of duplicating infrastructure, agonizing over the tools and components for each ‘unique’ use case, grappling with security concerns, and ultimately navigating the complex realm of…
-
How we built a dynamic Kubernetes API Server for the API Aggregation Layer in Cozystack
Hi there! I’m Andrei Kvapil, but you might know me as @kvaps in communities dedicated to Kubernetes and cloud-native tools. In this article, I want to share how we implemented our own extension api-server in the open-source PaaS platform, Cozystack. Kubernetes truly amazes me with its powerful extensibility features. You’re probably already familiar with the…
-
Gateway API v1.2: WebSockets, Timeouts, Retries, and More
Kubernetes SIG Network is delighted to announce the general availability of Gateway API v1.2! This version of the API was released on October 3, and we’re delighted to report that we now have a number of conformant implementations of it for you to try out. Gateway API v1.2 brings a number of new features to…
-
Kubernetes v1.32: Penelope
Editors: Matteo Bianchi, Edith Puclla, William Rizzo, Ryota Sawada, Rashan Smith Announcing the release of Kubernetes v1.32: Penelope! In line with previous releases, the release of Kubernetes v1.32 introduces new stable, beta, and alpha features. The consistent delivery of high-quality releases underscores the strength of our development cycle and the vibrant support from our community.…
-
Kubernetes v1.32: QueueingHint Brings a New Possibility to Optimize Pod Scheduling
The Kubernetes scheduler is the core component that selects the nodes on which new Pods run. The scheduler processes these new Pods one by one. Therefore, the larger your clusters, the more important the throughput of the scheduler becomes. Over the years, Kubernetes SIG Scheduling has improved the throughput of the scheduler in multiple enhancements.…
-
Kubernetes v1.32: Memory Manager Goes GA
With Kubernetes 1.32, the memory manager has officially graduated to General Availability (GA), marking a significant milestone in the journey toward efficient and predictable memory allocation for containerized applications. Since Kubernetes v1.22, where it graduated to beta, the memory manager has proved itself reliable, stable and a good complementary feature for the CPU Manager. As…
-
Kubernetes v1.32 Adds A New CPU Manager Static Policy Option For Strict CPU Reservation
In Kubernetes v1.32, after years of community discussion, we are excited to introduce a strict-cpu-reservation option for the CPU Manager static policy. This feature is currently in alpha, with the associated policy hidden by default. You can only use the policy if you explicitly enable the alpha behavior in your cluster. Understanding the feature The…
-
Enhancing Kubernetes API Server Efficiency with API Streaming
Managing Kubernetes clusters efficiently is critical, especially as their size is growing. A significant challenge with large clusters is the memory overhead caused by list requests. In the existing implementation, the kube-apiserver processes list requests by assembling the entire response in-memory before transmitting any data to the client. But what if the response body is…