You've likely heard the adage, "Contributing isn't just about
writing code", whispered in forums or seen etched into the digital
walls of open source communities.But what depth of truth lies
within this ancient wisdom, especially in the vast, evolving world
of Kubernetes? Today, contributing to open source extends far
beyond the realm of coding.It's an inclusive journey that welcomes
the diverse skills of all who wish to be a part of it.Whether
you're a seasoned developer or someone whose strengths lie outside
traditional programming, your contributions hold immense value.
Imagine yourself
Following the GA release of Gateway API
last October, Kubernetes SIG Network is pleased to announce the
v1.1 release of Gateway
API.In this release, several features are graduating to
Standard Channel (GA), notably including support for
service mesh and GRPCRoute.We're also introducing some new
experimental features, including session persistence and client
certificate verification.
What's new
Graduation to Standard
This release includes the graduation to Standard of four eagerly awaited features.This means they are no longer experimental concepts;inclusion in the Standard release channel denotes a high
The Kubernetes Container Runtime Interface (CRI) acts as the main
connection between the kubelet and the Container Runtime.Those runtimes have to
provide a gRPC server which has to fulfill a Kubernetes defined
Protocol Buffer interface.This API definition evolves over time, for
example when contributors add new features or fields are going to
become deprecated. In this blog post, I'd like to dive into the
functionality and history of three extraordinary Remote Procedure
Calls (RPCs), which are truly outstanding in terms of how they
work:
With the release of Kubernetes 1.30, the feature to prevent the
modification of the volume mode of a PersistentVolumeClaim that was created from an
existing VolumeSnapshot in a Kubernetes cluster, has moved to GA!
The problem
The Volume Mode of a PersistentVolumeClaim refers to whether the underlying volume on the storage device is formatted into a filesystem or presented as a raw block device to the Pod that uses it. Users can leverage the VolumeSnapshot feature, which has been stable since Kubernetes v1.20, to create a PersistentVolumeClaim (shortened
With Kubernetes 1.30, we (SIG Auth) are moving Structured
Authorization Configuration to beta. Today's article is about
authorization:deciding what someone can and cannot
access.Check a previous article from yesterday to find about what's
new in Kubernetes v1.30 around authentication (finding out
who's performing a task, and checking that they are who they say
they are).
Introduction
Kubernetes continues to evolve to meet the intricate requirements of system administrators and developers alike.A critical aspect of Kubernetes that ensures the security and integrity of the cluster is theWeitere Beiträge ...
Seite 1 von 20