tag: Deprecation · 18 items
- Platform/SRE — Plan: ingress-nginx is one of the most widely deployed Kubernetes ingress controllers; its retirement means planning a migration to an alternative (Gateway API, Traefik, Emissary, etc.) before it goes unmaintained. No hard deadline surfaced in signals, so schedule migration evaluation this quarter.
- CI/CD — Skip
- Leader — Plan: Organizations standardized on ingress-nginx will need to choose and adopt a replacement ingress strategy; evaluate Gateway API or alternative controllers and factor the migration into the next infrastructure planning cycle.
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: Kubernetes 1.35 (currently GA, EOL 2027-02-28) defaults failCgroupV1 to true, meaning kubelet refuses to start on cgroup v1 nodes without an explicit override. Audit all Linux nodes for cgroup version and complete migration to cgroup v2 before upgrading any cluster to 1.35 or later.
- CI/CD — Skip
- Leader — Skip
- Signals: Kubernetes 1.31 is past EOL (2025-11-11, 330d ago) · Kubernetes 1.25 is past EOL (2023-10-27, 1076d ago) · Kubernetes 1.35 EOL 2027-02-28 · deprecation mentioned (no explicit date found)
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: Copilot model deprecations took effect October 2, 2026, affecting all Copilot experiences including code completions and agent modes; review which models your teams rely on and confirm any workflow or policy updates needed before breakage occurs.
- Signals: deprecation/EOL deadline mentioned: October 2, 2026
- Platform/SRE — Act: If your org uses GitHub Enterprise Cloud with data residency, audit any internal tooling, Terraform GitHub provider clients, or API automation that may negotiate TLS using only X25519 before October 7 — connections from those clients will break.
- CI/CD — Act: Verify that CI runners and pipeline scripts connecting to GHE.com with data residency use a TLS stack that offers multiple key-agreement algorithms, not X25519 exclusively; the hard cutoff is October 7, 2026.
- Leader — Skip
- Platform/SRE — Plan: Azure Functions v1 apps hosted on Container Apps will stop processing requests after September 29, 2027; inventory affected workloads and schedule migration to a supported hosting model (v2 or later) well before that date.
- CI/CD — Skip
- Leader — Plan: The forced retirement of Azure Functions v1 on Container Apps by September 29, 2027 is a migration project to scope this planning cycle — assess affected workloads, estimate re-platforming costs, and assign ownership before the deadline pressure grows.
- Signals: deprecation/EOL deadline mentioned: September 29, 2027
- Platform/SRE — Skip
- CI/CD — Plan: Pipelines that download codeql-bundle.tar.gz or .tar.zst need to migrate to platform-specific CodeQL bundles; no hard removal date announced yet, so audit your CodeQL download steps and update references to the appropriate per-platform bundle this quarter.
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: This GA release deprecates the containerd.io/runtime-allow-mounts shim annotation (replaced by MountCapabilities extension) and task API address/version fields in runc options; plan migration away from both, though no removal date is confirmed yet.
- CI/CD — Skip
- Leader — Skip
- Signals: containerd 2.4 EOL 2027-05-16 · deprecation mentioned (no explicit date found)
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: GitHub is retiring specific Copilot models across all experiences (completions, chat, agent mode) on October 19, 2026. If your org has standardized on GitHub Copilot and any internal tooling or developer configs hardcode model selections, ensure teams audit and update those configurations before the deadline.
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: Teams hosting or consuming Vagrant boxes via HCP should identify an alternative registry (self-hosted or otherwise) and plan migration before HCP Vagrant shuts down; no specific cutoff date is published yet, so treat this as a Q4 2026 planning item.
- CI/CD — Skip
- Leader — Learn: HashiCorp sunsetting HCP Vagrant signals continued consolidation of their cloud platform away from legacy VM-based dev tooling; worth noting if Vagrant is still part of the org’s standard developer environment stack.
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Act: If running the containerized SAP data connector, the images are removed October 14, 2026 — migrate to a supported log-forwarding method before that date to avoid broken data ingestion.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: October 14, 2026; September 14, 2026
- Platform/SRE — Plan: SHA-1 HTTPS on GitHub is now enforced (2026-09-15); audit any infrastructure tooling—Terraform module fetches, Helm chart sources, custom operators—that connects to GitHub via HTTPS and update any clients running legacy TLS libraries before they surface connectivity failures.
- CI/CD — Act: Enforcement is live as of 2026-09-15—any runner image or build tool using an old TLS stack that negotiates SHA-1 for HTTPS connections to GitHub is already failing; audit runner images and git client versions immediately and update or replace those using legacy OpenSSL/TLS configurations.
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Act: Migrate AKS node pools off Azure Linux with OS Guard to Azure Container Linux before December 10, 2026 — after that date, creation of new nodes with that OS config will be blocked.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: December 10, 2026
- Platform/SRE — Plan: The gcloud minikube component will be removed after January 31, 2027 — schedule migration to a standalone minikube install or alternative local-cluster tooling before that date. Cloud Monitoring’s per-chart time-range override is now GA and worth adopting for long-duration observability dashboards alongside high-frequency charts.
- CI/CD — Plan: If any pipelines invoke gcloud’s minikube component for integration-test clusters, plan migration to a standalone minikube binary before the January 31, 2027 removal; also audit scripts for the already-deprecated
gcloud storage buckets anywhere-caches pausecommand and replace it in affected workflows. - Leader — Skip
- Signals: deprecation/EOL deadline mentioned: 2026-09-09; January 31, 2027 · GA announcement · breaking-change flagged
- Platform/SRE — Skip
- CI/CD — Plan: If pipelines use Copilot API integrations or automation referencing specific deprecated models, update model references before October 2, 2026 to avoid broken AI-assisted workflows.
- Leader — Plan: Copilot model deprecation on October 2, 2026 may affect teams relying on specific models for coding workflows; assess which models are in use and communicate the migration timeline to engineering teams this quarter.
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: Copilot model deprecations took effect September 1, 2026 — verify which models your org relies on in Copilot Chat, completions, or agent mode are still available, and update any tooling or policy that specified a now-removed model.
- Signals: deprecation/EOL deadline mentioned: September 1, 2026
- Platform/SRE — Act: If you run the containerized SAP data connector agent for Microsoft Sentinel, migrate to the replacement agent before September 14, 2026, when the agent will be permanently disabled and SAP log ingestion will stop.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: September 14, 2026
- Platform/SRE — Skip
- CI/CD — Plan: If any pipelines invoke MAI-Code-1-Flash via GitHub Copilot APIs or extensions, migrate to MAI-Code-1.1-Flash before September 10, 2026 to avoid breakage.
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: September 10, 2026
- Platform/SRE — Plan: ingress-nginx is one of the most widely deployed Kubernetes ingress controllers; its retirement means planning a migration to an alternative (e.g., Envoy Gateway, NGINX Gateway Fabric, or another Gateway API-conformant controller). No forced migration date is confirmed yet, so scope the migration project now before community support winds down.
- CI/CD — Skip
- Leader — Plan: If ingress-nginx is part of the org’s Kubernetes golden path or standard stack, its retirement requires evaluating replacement ingress controllers and updating platform standards; begin that toolchain review this planning cycle before the project loses maintainer support.
- Signals: deprecation mentioned (no explicit date found)