Kubernetes News Digest: Anti‑Discrimination Docs, 1.19 Beta Freeze, Linkerd 2.8, and New Open‑Source Tools
This roundup highlights recent Kubernetes ecosystem changes, including the addition of anti‑discrimination statements to documentation, the upcoming 1.19.0‑beta.1 code freeze, Linkerd 2.8 multi‑cluster support, several upstream enhancements, and curated open‑source project and reading recommendations for cloud‑native practitioners.
Industry News
All Kubernetes documentation now includes a header declaring an anti‑discrimination stance, and both the Kubernetes and Go codebases have replaced terms such as whitelist/blacklist and master/slave with more inclusive language.
Kubernetes 1.19.0‑beta.1 is scheduled for code freeze on June 25, after which release and testing will commence.
Linkerd 2.8 has been officially released, adding multi‑cluster capabilities that allow secure, transparent connections across multiple Kubernetes clusters independent of network topology.
Upstream Progress
The CertificateSigningRequest v1 API is now supported in the controller, client‑go, and kubectl, with changes to fields like spec.signerName, spec.usages, and status.conditions compared to the v1beta1 version.
kubectl and client‑go now expose server‑side warnings, and the generic scheduler has removed certain log messages to improve preemption evaluation performance.
The kubelet now adds iptables rules to drop non‑local packets crossing the localhost boundary.
The RotateKubeletClientCertificate feature has been promoted to GA, and its feature‑gate will be removed in version 1.20.
A standard for configuring local registries across Kind, K3d, Minikube, and MicroK8s has been introduced.
Performance improvements include passing RangeOptions.limit down the MVCC index tree to reduce memory overhead during range queries, and optimizing memory usage for range‑count operations.
Open‑Source Project Recommendations
xlskubectl : Manage your Kubernetes clusters using Excel spreadsheets.
k8s-image-availability-exporter : A Prometheus exporter that checks the status of container images defined in Kubernetes objects.
CRIU : A user‑space checkpoint/restore tool that captures complete process state (process tree, file descriptors, memory mappings, etc.) to the filesystem and can later restore the process.
Weekly Reading Recommendations
When it's not only about Kubernetes CVE – a case study of discovering a Kubernetes vulnerability, conducting analysis, and submitting a CVE.
Beda, Burns and Mcluckie: the Creators of Kubernetes Look Back – a retrospective on the early developers and the birth of Kubernetes.
Multi‑cluster Kubernetes with Ambassador and Linkerd – explains how Linkerd 2.8 can be combined with Ambassador Edge Stack to achieve cross‑cluster communication and service management.
Using Prometheus to Monitor Kubernetes: The Most Practical Deployment – guides readers on building a comprehensive Prometheus monitoring system on top of a Kubernetes cluster, reflecting the broader rise of cloud‑native technologies.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Alibaba Cloud Native
We publish cloud-native tech news, curate in-depth content, host regular events and live streams, and share Alibaba product and user case studies. Join us to explore and share the cloud-native insights you need.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
