tag: Aks · 6 items
- Platform/SRE — Plan: Windows Server 2025 is now a supported node OS on AKS, giving teams a clear upgrade target as older Windows Server versions approach end of support. Schedule evaluation of Windows node pool migration this quarter, especially if running 2019 or 2022 nodes — no forced-upgrade date is signaled yet, but the deprecation mention warrants adding it to the roadmap.
- CI/CD — Skip
- Leader — Learn: AKS now supports Windows Server 2025, extending the viability of Windows-based workloads on managed Kubernetes — useful context if the org is evaluating its Windows modernization strategy, but no strategic or cost decision is required now.
- Signals: deprecation mentioned (no explicit date found) · GA announcement
- Platform/SRE — Plan: Artifact streaming on AKS+ACR is now GA and can reduce pod startup latency during scale-out events; evaluate enabling it for workloads where image pull time is a bottleneck this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: This GA capability lets AKS pods authenticate to SMB file shares via workload identity instead of node-level managed identity, improving least-privilege posture. Evaluate replacing existing managed-identity-based Azure Files mounts with workload identity bindings in your next infrastructure review cycle.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: GA Bastion-to-AKS tunneling removes the need for a public API server endpoint or VPN for cluster access; evaluate adopting this as the standard private-cluster access pattern in your AKS environments this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Learn: Public preview feature for reducing AKS node startup times on GPU/AI/Windows workloads by pre-baking images; worth evaluating if you run performance-sensitive node pools, but not actionable until GA.
- CI/CD — Skip
- Leader — Skip
- Signals: pre-GA (alpha/beta/RC/preview)
- Platform/SRE — Plan: The Kubernetes Gateway API is the intended successor to the Ingress API, and it’s now GA on AKS — plan a migration evaluation from existing Ingress controllers to the managed Gateway API offering this quarter. No forced deadline exists, but adopting early reduces future migration debt as the Ingress API ages out.
- CI/CD — Skip
- Leader — Learn: Gateway API going GA on AKS signals accelerating industry standardization on the new Kubernetes networking model, worth tracking as context for ingress-tooling decisions if an AKS golden-path review is upcoming.
- Signals: GA announcement