Kubernetes - 2

2026 (12)

February (10)

k8s: Before You Migrate: Five Surprising Ingress-NGINX Behaviors You Need to Know

Kubernetes Official Blog

2026-02-27

Kubernetes will retire the community Ingress-NGINX controller in March 2026; this post lists five non-obvious routing/rewriting/redirect behaviors that can cause outages when translating to Gateway API unless explicitly replicated.

azure: [In preview] Public Preview: Secure ingestion and pod placement for Azure Monitor pipeline

Azure Updates

2026-02-26

Azure Monitor pipeline adds public-preview support for secure ingestion from external endpoints using TLS/mTLS and Bring Your Own Certificates (BYOC), plus new controls for pod placement.

azure: [In preview] Public Preview: Cluster mode for the agentic CLI for AKS

Azure Updates

2026-02-18

AKS agentic CLI adds a public preview “cluster mode” to run diagnostic agents with reduced inherited user permissions and avoid per-user deployments.

azure: [Launched] Generally Available: Node auto-provisioning support in Azure government and private cloud

Azure Updates

2026-02-18

AKS node auto-provisioning is now generally available in Azure Government and Azure private cloud environments.

aks: Release 2026-02-08

Release notes from AKS

2026-02-17

AKS release 2026-02-08 adds new Kubernetes patch versions, expands regional availability for API Server VNET Integration, and introduces several security/behavioral changes plus multiple component/image updates.

azure: [Launched] Generally Available: AKS support for Kubernetes version 1.34

Azure Updates

2026-02-13

AKS now generally supports Kubernetes v1.34. The upstream v1.34 release includes 58 enhancements across feature maturity levels.

k8s: Spotlight on SIG Architecture: API Governance

Kubernetes Official Blog

2026-02-12

Interview with Jordan Liggitt describing SIG Architecture’s API Governance subproject: it defines and enforces conventions across Kubernetes API surfaces to balance stability/compatibility with ongoing evolution.

azure: [Launched] Generally Available: Azure Container Storage v2.1.0 now with Elastic SAN integration and on demand installation

Azure Updates

2026-02-03

Azure Container Storage v2.1.0 is generally available, adding native Elastic SAN support and a lightweight on‑demand installation model to simplify deployment and operations for Kubernetes workloads on Azure.

azure: [In preview] Public Preview: Azure Kubernetes Fleet Manager namespace-scoped resource placement

Azure Updates

2026-02-03

Azure Kubernetes Fleet Manager now offers namespace‑scoped resource placement in public preview, providing fine‑grained control to select and propagate individual namespace resources across multiple clusters.

k8s: Introducing Node Readiness Controller

Kubernetes Official Blog

2026-02-03

The Node Readiness Controller is a new Kubernetes project that provides a declarative system (NodeReadinessRule) to manage node taints based on custom node conditions. It extends readiness guardrails during node bootstrapping and runtime by automating taint application/removal so workloads land only on nodes that meet infrastructure-specific requirements.

January (2)

k8s: New Conversion from cgroup v1 CPU Shares to v2 CPU Weight

Kubernetes Official Blog

2026-01-30

An improved, non-linear conversion from cgroup v1 CPU shares to cgroup v2 CPU weight replaces the previous linear formula to restore intended priority relationships and improve granularity for small CPU requests. The change is implemented in OCI runtimes (runc >=1.3.2, crun >=1.23) and may require updates to tooling that assumed the old mapping.

k8s: Ingress NGINX: Statement from the Kubernetes Steering and Security Response Committees

Kubernetes Official Blog

2026-01-29

Kubernetes Steering and Security Response Committees announced Ingress NGINX will be retired in March 2026. There will be no further releases, bug fixes, or security patches. Roughly 50% of cloud-native environments rely on it, so many clusters are at risk unless teams check and migrate; alternatives (Gateway API or third‑party Ingress controllers) are not direct drop‑in replacements and require planning and engineering time. There are about two months to prepare.