verdict: Plan · 468 items
- Platform/SRE — Plan: If you run Amazon MSK, this GA feature lets managed Prometheus collectors scrape consumer-group lag metrics without self-operated agents; evaluate adopting it this quarter to replace any self-managed Kafka exporters in your observability pipeline.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: New GA capability worth evaluating this quarter: enabling automatic SDK integration on existing CloudFront web ACLs that use Bot Control (targeted), ATP, or ACFP rule groups eliminates per-application script-tag maintenance and reduces misconfiguration risk. Review your WAF web ACLs and enable the setting via Console, CLI, CDK, or CloudFormation.
- CI/CD — Skip
- Leader — Learn: This reduces recurring per-application engineering overhead for teams protecting many CloudFront-fronted properties with advanced WAF rule groups — useful context when assessing operational cost of the WAF managed-rule investment, but no strategic decision is required.
- Platform/SRE — Plan: MSK Provisioned clusters now support TLS 1.3 as a GA opt-in via named security policies — evaluate applying a TLS 1.3-capable policy this quarter, particularly if your org has compliance frameworks requiring TLS 1.3 or if post-quantum readiness is on the roadmap.
- CI/CD — Skip
- Leader — Learn: MSK’s new TLS 1.3 support is a step toward post-quantum cryptography readiness and aligns with tightening compliance standards; no strategic or licensing decision is forced, but worth knowing if your security policy roadmap includes post-quantum preparedness.
- Platform/SRE — Plan: If your org maintains a firewall or security-group allowlist for incoming GitHub webhook traffic, update it to include the new IP ranges from the Meta API hooks field before deployments that rely on webhooks start failing.
- CI/CD — Plan: Pipelines that trigger via GitHub webhooks and sit behind a strict inbound allowlist may silently drop deliveries; pull the updated ranges from the Meta API and refresh your allowlist rules.
- Leader — Skip
- Platform/SRE — Plan: Azure MCP Server 3.0 is now GA with expanded Terraform/IaC integration, making AI-agent-driven Azure resource management more viable; evaluate whether it fits your infrastructure automation workflow this quarter — no forced migration or deadline involved.
- CI/CD — Skip
- Leader — Learn: Azure MCP Server 3.0 GA signals growing maturity of AI-agent-to-cloud-API tooling; worth tracking as context for AI-assisted platform engineering strategy, but no immediate toolchain or cost decision is triggered.
- Signals: GA announcement · major release (3.0)
- Platform/SRE — Plan: If you’re running DataSync tasks against FSx for Windows File Server or NetApp ONTAP, Enhanced mode is now fully compatible and offers parallel processing plus no file-count limits over Basic mode — worth scheduling an evaluation and migrating existing tasks this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Teams running MSK Connect can now update connector plugins and worker configurations without deleting and recreating connectors, preserving committed offsets; evaluate adopting this for your next connector upgrade cycle to reduce disruption risk.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Managed Grafana 13.2 is now GA with Git Sync for dashboard-as-code, dynamic dashboards, and PromQL in the CloudWatch data source — worth scheduling an upgrade this quarter; no forced-upgrade deadline exists for version 12.4, so no clock is running.
- CI/CD — Skip
- Leader — Skip
- Signals: Grafana 13.2 EOL 2027-05-18 · GA announcement
- Platform/SRE — Plan: Grafana 13.3 is a new GA minor for a core observability stack tool; schedule an upgrade this quarter to gain Notebooks and the UI refresh — cross-dashboard variables are still public preview, so hold off on that feature specifically until GA.
- CI/CD — Skip
- Leader — Skip
- Signals: Grafana 13.3 EOL 2027-07-20
- Platform/SRE — Skip
- CI/CD — Plan: GitLab Orbit is now GA and directly improves AI agent efficiency in CI/CD workflows — pipeline context, vulnerability data, and ownership are queryable in one graph. Teams using AI-assisted GitLab pipelines should evaluate adopting Orbit MCP integration to reduce agent retry churn and token spend.
- Leader — Learn: The 4.5x token reduction claim is a concrete data point for anyone budgeting AI agent usage on GitLab; worth tracking as a cost-optimization lever when planning AI toolchain investments, but no decision is required now.
- Signals: GA announcement
- Platform/SRE — Plan: If you run Azure Container Apps with Log Analytics as the logging destination, Microsoft has marked it legacy and recommends migrating to Azure Monitor; no forced removal date is given, but schedule the migration before it becomes a breaking change.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: GA capability that can cut cold-start latency up to 70% for large Lambda container workloads; evaluate adding SOCI index creation to ECR push workflows for any function images over a few hundred MB this quarter.
- CI/CD — Learn: Adopting SOCI requires a new pipeline step (generate SOCI index, push a second tagged manifest to ECR), but it is fully opt-in with no deadline — worth noting as a future build-pipeline enhancement if cold starts are a pain point.
- Leader — Skip
- Platform/SRE — Plan: New GA capability lets platform teams build automated identity lifecycle workflows — audit Lambda functions, SIEM alerts, or downstream access revocation triggered by group/user changes. Worth incorporating into identity management automation this quarter if IAM Identity Center is the identity source.
- CI/CD — Skip
- Leader — Learn: EventBridge-driven identity change events can strengthen automated compliance and audit posture for organizations managing large workforces in AWS; no strategic vendor or cost decision required, but informs thinking on identity automation capabilities.
- Platform/SRE — Plan: Enable EKS Dashboard trusted access via AWS Organizations to get consolidated CA rotation status across all clusters and regions — clusters created since 2018 carry 10-year CAs that are now entering the window where rotation planning should begin. No hard expiration deadline is cited, but this is a free GA capability worth enabling this quarter to surface clusters approaching rotation.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: EKS Auto Mode now natively manages Gateway API resources (Gateway, HTTPRoute) including weighted routing, header-based routing, and ACM TLS — eliminating the need for a separate ingress controller. Evaluate adopting Gateway/HTTPRoute as the standard traffic-management pattern for EKS Auto Mode clusters this quarter.
- CI/CD — Skip
- Leader — Learn: EKS Auto Mode’s native Gateway API support signals Kubernetes standardizing on a single next-gen ingress model; worth tracking as a data point when reviewing golden-path networking standards for EKS-based platforms.
- Platform/SRE — Plan: New GA ECS capability that packs tasks across multiple underutilized instances and consolidates Spot capacity — worth evaluating this quarter if you operate ECS Managed Instances with narrow instance-type capacity providers to improve utilization and reduce EC2 spend.
- CI/CD — Skip
- Leader — Learn: Cross-instance and Spot consolidation in ECS Managed Instances is a FinOps-relevant feature for ECS-heavy orgs, but it’s a new GA optimization capability rather than a pricing or vendor-risk event — no strategic decision required now.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: If your org pays for GitHub Enterprise and Copilot separately, this bundling change is worth reviewing with your account team to consolidate licensing and potentially reduce complexity or cost. No deadline, but address it in the next contract or planning cycle.
- Platform/SRE — Skip
- CI/CD — Plan: Evaluate enabling Dependabot reachability analysis to triage which vulnerable dependencies are actually callable from your code, reducing alert noise and helping the team focus remediation effort on real exposure.
- Leader — Skip
- Platform/SRE — Learn: GA automation for issue triage and CI failure analysis could reduce toil on shared infra, but there’s no operational urgency or infrastructure surface change — worth watching as the tooling matures.
- CI/CD — Plan: Now GA, GitHub Agentic Workflows can automate CI failure analysis and triage directly in the pipeline; evaluate adopting it this quarter to reduce manual investigation overhead across teams.
- Leader — Learn: A new GA open-source automation layer from GitHub Next that could eventually inform the org’s golden path for AI-assisted DevOps, but no licensing, cost, or strategic decision is required yet.
- Signals: GA announcement
- Platform/SRE — Plan: GA feature that meaningfully changes GPU capacity planning on ECS — teams running small-model inference or multi-model serving should evaluate adopting MPS sharing to improve GPU utilization and reduce per-workload instance costs this quarter.
- CI/CD — Skip
- Leader — Learn: GPU workload cost density improvement is worth noting for teams with ML inference spend on ECS, but adoption is optional and operational — no strategic vendor, licensing, or pricing-model decision required.
- Platform/SRE — Plan: AWS KMS now GA with all three ML-KEM key specs, backed by FIPS 140-3 HSMs — evaluate adopting ML-KEM for workloads handling long-lived sensitive data as part of a PQC migration plan this quarter; no forced deadline, but the NIST IR 8547 roadmap signals classical key-exchange schemes will be phased out.
- CI/CD — Skip
- Leader — Learn: AWS KMS adding ML-KEM signals cloud providers are operationalizing NIST’s PQC standards; useful context for shaping a post-quantum cryptography roadmap, but no licensing change, cost impact, or deadline requires a decision now.
- Platform/SRE — Plan: This GA capability removes the need for overly broad IAM roles in multi-Region architectures, enabling per-user fine-grained access control and audit trails across Regions. Teams running distributed or disaster-recovery workloads on AWS should evaluate updating their IAM Identity Center configuration and multi-Region access patterns this quarter.
- CI/CD — Skip
- Leader — Learn: Cross-Region identity propagation tightens the audit and access-control story for multi-Region AWS deployments without additional cost, which may eventually inform golden-path standards for identity architecture, but no strategic decision is required now.
- Platform/SRE — Plan: New GA capability that changes how external query engines and partners authenticate to Glue-hosted Iceberg tables — teams running Iceberg on Glue should evaluate replacing SigV4 paths with OAuth token exchange to eliminate credential distribution to third-party analytics platforms.
- CI/CD — Skip
- Leader — Learn: OAuth-based federated access to Iceberg tables without distributing AWS credentials is a meaningful shift in data-partnership architecture, relevant for orgs negotiating third-party analytics integrations, but no immediate strategic decision is triggered.
- Platform/SRE — Plan: New GA capability lets you enable Launch Before Terminate once at the account level via PutAccountSetting, ensuring full capacity is maintained during instance refreshes, rebalancing, and health-check replacements across all ASGs. Worth scheduling a review and enabling this quarter to reduce availability risk during replacement events.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA ECR capability eliminates the manual retag workaround for backfilling existing images to replication destinations — worth scheduling adoption for teams expanding to new regions or validating DR readiness. No deadline, but evaluate this quarter if multi-region image parity is a compliance or DR requirement.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: etcd backs every Kubernetes control plane, and a breaking change in a patch release demands a CHANGELOG review before upgrading; review the upgrade guide and validate cluster behavior in staging before rolling this out to production — no forced deadline yet.
- CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: etcd v3.6.16 carries a flagged breaking change in a patch release, which is atypical — review the changelog and upgrade guide before applying, since etcd is the Kubernetes control-plane backing store and an unexpected breakage can bring down cluster state. No hard deadline, but treat this as a deliberate upgrade rather than a routine patch rollout.
- CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: Unusual for a patch release, v3.5.35 carries a breaking-change flag; review the etcd CHANGELOG and upgrade guide before applying this to any cluster running etcd 3.5.x to avoid unexpected behavior in the control-plane data store.
- CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: Removes trust for compromised eMudhra CA private keys from Envoy’s trust store; any 1.37.x deployment trusting those CAs is exposed to fraudulent cert acceptance. No KEV listing or confirmed active exploitation, so cap is Plan — schedule patching to 1.37.10 this sprint; 1.37 itself EOLs 2027-01-13.
- CI/CD — Skip
- Leader — Skip
- Signals: Envoy 1.37 reaches EOL in 79d (2027-01-13)
- Platform/SRE — Plan: Two breaking changes affect teams running Backstage: the catalog backend now rejects primitive-root filter predicates (any custom catalog queries or plugins using that pattern must be updated), and the Atlassian usernameMatchingUserEntityName resolver is removed (migrate to emailMatchingUserEntityProfileEmail). No forced deadline, but plan the upgrade and audit affected code before rolling this version out.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: New GA capabilities in GitHub secret scanning—validity checks, dismissals, API, and webhooks—are worth integrating this quarter to automate triage and response when pipeline credentials or tokens are exposed in public repos.
- Leader — Learn: GitHub’s expanded secret-monitoring surface (validity checks, webhooks, API) shapes how orgs can build automated security workflows around leaked credentials, but no licensing, pricing, or vendor-risk decision is triggered.
- Platform/SRE — Skip
- CI/CD — Plan: GitHub Apps can now replace classic PATs for enterprise-wide automation; schedule an audit of existing PAT-based pipeline credentials and migrate to GitHub App installations for tighter scope and auditability — no forced deadline, but a clear security improvement to queue this quarter.
- Leader — Learn: This GA capability enables org-wide policy to standardize on GitHub Apps over classic PATs for automation, which strengthens credential hygiene and reduces blast radius of leaked tokens; worth factoring into enterprise GitHub governance standards but no immediate decision required.
- Signals: GA announcement
- Platform/SRE — Plan: Teams using Cloud SQL Auth Proxy must upgrade to 2.26.3+, Cloud SQL Proxy Operator to 1.8.4+, and Ops Agent to 2.73.0 to address this Go root-certificate vulnerability (GCP-2026-071); managed Cloud SQL instances are auto-patched during scheduled maintenance. CVE is not KEV-listed and EPSS is 0.00, so no active exploitation warrants immediate emergency action, but proxy upgrades are concrete tasks to schedule this sprint.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-111943 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: If you run Azure VMs on Premium SSDv2 or Ultra disks, this GA feature enables granular file/folder recovery rather than full-disk restores — worth adopting this quarter if ILR was previously a gap in your backup strategy.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: This GA capability eliminates the need for a NAT appliance or IP renumbering when connecting networks with overlapping CIDRs — directly relevant if the org has pending M&A integration, partner VPN, or multicloud connectivity work blocked by address conflicts. Evaluate adding to the network-connectivity pattern for such scenarios this quarter.
- CI/CD — Skip
- Leader — Learn: Managed 1:1 NAT on Transit Gateway removes the appliance cost and renumbering complexity historically incurred during M&A network integration; worth noting as an option when assessing future acquisition or partner-connectivity scope.
- Platform/SRE — Plan: If you run MSK Connect, update your maintenance runbooks to use pause/resume instead of delete/recreate — this preserves offsets and config, reducing risk during source/sink maintenance windows. No deadline; schedule adoption this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: A 30% reduction in EMR on EKS per-vCPU and per-GB charges applies automatically with no action required — validate the cost impact in your next FinOps review and update budget forecasts for Spark workloads on EKS accordingly.
- Platform/SRE — Plan: Platform teams pulling providers and modules from the public Terraform Registry are subject to the revised ToS; review the updated terms and evaluate whether to implement a provider network mirror or private registry to ensure automated and commercial usage remains compliant.
- CI/CD — Plan: CI pipelines that run
terraform initagainst the public registry are exposed to ToS restrictions on automated usage; audit pipeline patterns and consider mirroring providers or switching to the OpenTofu registry to keep builds compliant. - Leader — Plan: This ToS change compounds the earlier BSL relicensing as a vendor-risk signal for orgs standardized on Terraform; use this moment to formally evaluate OpenTofu as the org’s IaC standard and assess whether current Registry usage complies with the new terms before the next planning cycle.
- Platform/SRE — Skip
- CI/CD — Plan: Two critical PHP CVEs affect Docker images built on PHP; audit pipelines for PHP-based container images and update base images to patched PHP versions. Neither CVE is KEV-listed and EPSS scores are low (0.12/0.06), so no emergency, but schedule the base-image refresh this sprint.
- Leader — Skip
- Signals: CVE-2026-109618 — CISA KEV: not listed, EPSS 0.12, reported by 2 collected sources · CVE-2026-109619 — CISA KEV: not listed, EPSS 0.06, reported by 2 collected sources
- Platform/SRE — Skip
- CI/CD — Plan: If your runners operate behind strict outbound firewall or IP allowlist rules, review and update allowlists to include the new GitHub Actions blob storage endpoints surfaced in the meta API — no deadline given, but unpatched allowlists could silently break artifact uploads or caching.
- Leader — Skip
- Platform/SRE — Plan: If you self-host GitLab, schedule an upgrade to the relevant patched branch (19.5.1, 19.4.3, 19.3.6, etc.) this sprint; GitLab’s ‘Critical’ designation signals high-severity CVEs, but no KEV listing or active exploitation is confirmed in the signals, so this is urgent planned work rather than a drop-everything hotfix.
- CI/CD — Plan: Teams running self-hosted GitLab CI should upgrade to the appropriate patched version for their minor branch; a critical security fix in the CI/CD platform itself is a supply-chain risk that warrants scheduling an upgrade this sprint, even without confirmed exploitation.
- Leader — Skip
- Signals: major release (19.0)
- Platform/SRE — Plan: This GA capability closes a real security gap by validating destination IPs against Route 53-resolved addresses, extending domain-based filtering to SFTP, SSH, and other protocols beyond HTTP/HTTPS. Evaluate adding Route 53 Resolved IP Validation to existing Network Firewall policies to harden egress controls and prevent SNI spoofing.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Several new GA Grafana Cloud capabilities — including always-on Assistant Watchers that detect anomalies outside predefined alert rules — are worth evaluating for teams running Grafana Cloud as their observability platform. No hard deadline, but the features are GA and relevant to how observability stacks are architected this quarter.
- CI/CD — Skip
- Leader — Learn: Grafana Labs is positioning Grafana Cloud toward AI-assisted autonomous operations; understanding this capability direction is useful context for observability platform strategy and build-vs-buy decisions, but no pricing change or vendor risk event requires a decision now.
- Signals: GA announcement
- Platform/SRE — Plan: If your org runs Grafana Cloud, the Knowledge Graph’s GA expansion — connecting service catalog, on-call ownership, and past-incident context into a unified runtime view — is worth evaluating this quarter to improve investigation workflows and reduce MTTR.
- CI/CD — Skip
- Leader — Learn: The direction of shared observability context for both humans and AI agents (via open standards) shapes thinking about platform-wide incident tooling strategy, though no vendor or toolchain decision is forced by this announcement.
- Platform/SRE — Plan: Assistant Watchers and Investigations are now GA in Grafana Cloud, adding AI-driven monitoring and automated evidence gathering to the observability workflow — evaluate adopting these for on-call runbooks this quarter; Managed Sandboxes remain public preview so hold off on that piece.
- CI/CD — Skip
- Leader — Learn: Grafana’s GA AI incident-response features signal a maturing market for AI-augmented observability — useful context for evaluating where AI tooling fits in the platform strategy, but no immediate decision required.
- Signals: GA announcement
- Platform/SRE — Plan: New GA managed service for Terraform execution on GCP could replace self-managed Terraform runners for platform teams standardized on GCP; evaluate whether to adopt Infrastructure Manager as the org’s Terraform execution layer this quarter.
- CI/CD — Skip
- Leader — Learn: Shifts the build-vs-buy calculation for GCP Terraform execution toward a managed option, but no licensing, cost, or vendor-risk forcing function exists yet.
- Platform/SRE — Skip
- CI/CD — Plan: If your repos still use legacy branch protection rules, schedule a migration to rulesets using this new bulk-convert action — rulesets offer better inheritance and auditability across org-wide pipelines.
- Leader — Skip
- Platform/SRE — Plan: Apigee X instances below 1-18-0-apigee-6 will be automatically updated within 7–21 days (by ~Nov 10). Verify your instances are not excluded due to the DNS misconfiguration in Known Issue 445936920 or use of the deprecated Apigee Java Library (removed Oct 16, 2025); excluded instances will be left on older versions.
- CI/CD — Plan: Cloud SDK 590.0.0 (released Oct 20) removes cloud-build-local and the app-engine-grpc component as breaking changes. Audit pipelines for any use of cloud-build-local for local Cloud Build testing and plan migration to alternatives before auto-upgrading the Cloud SDK to this version.
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: This new GA capability lets platform teams detach a DynamoDB replica into a standalone single-region table without recreating it — useful for regional isolation, offboarding a region, or audit scenarios. Worth evaluating if your platform runs global tables and needs cleaner multi-region lifecycle management.
- CI/CD — Skip
- Leader — Learn: Adds flexibility to multi-region DynamoDB architectures (including multi-account global tables), which may inform future data residency or regional isolation decisions, but no strategic action is required now.
- Platform/SRE — Plan: Finer-grained Azure Monitor signals can improve incident detection and trend analysis for Azure-based platforms; evaluate enabling advanced metrics across key resources this quarter.
- CI/CD — Skip
- Leader — Learn: Improved Azure Monitor granularity is a capability to be aware of for observability strategy, but no licensing, cost, or vendor-risk change is involved — no decision required now.
- Signals: GA announcement
- Platform/SRE — Plan: New GA capability removes a major operational barrier: migrating IAM Identity Center from Active Directory to an external IdP (Okta, Entra ID) no longer requires recreating users, groups, and permission assignments. If an AD-to-IdP identity migration is on the roadmap, schedule an evaluation of this simplified path.
- CI/CD — Skip
- Leader — Learn: This lowers the migration cost for orgs considering a shift from on-prem AD to a cloud IdP as their AWS identity source — a previously high-friction strategic move is now substantially simpler, which may shift the build-vs-buy calculus for identity infrastructure.
- Platform/SRE — Plan: New GA managed-service capability that changes how ECS ingress is architected — centralized ALB lifecycle management and ALB sharing across up to 25 services could simplify governance and reduce load balancer sprawl. Evaluate ECS Gateway as an alternative to custom ALB provisioning patterns in ECS environments this quarter.
- CI/CD — Skip
- Leader — Learn: ECS Gateway introduces a platform-team-governs, app-team-inherits model for ingress networking, and ALB sharing (up to 25 services) offers a cost optimization angle worth noting for FinOps reviews — but it forces no strategic decision today.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: Orgs standardized on GitHub Copilot Enterprise can now automate model policy governance via GET/PATCH REST endpoints; evaluate integrating this into policy-as-code workflows or org-wide AI model standards this planning cycle.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: If teams have hardcoded specific deprecated Copilot model identifiers in their IDE configs or API integrations, those workflows may already be broken as of today; audit Copilot model configurations org-wide and update any pinned references to supported models.
- Signals: deprecation/EOL deadline mentioned: October 19, 2026
- Platform/SRE — Plan: If your team uses EC2 Image Builder to bake AMIs or container base images, this GA opt-in feature eliminates per-build instance launch overhead by reusing warm ASG instances — worth evaluating this quarter for any image pipeline with meaningful build latency.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: If your pipelines use npm 12, pnpm 11/12, or Bun 1.4, you can now upgrade those package managers without losing Dependabot coverage — schedule the version bumps in your lockfiles and CI configs this quarter.
- Leader — Skip
- Platform/SRE — Plan: This GA feature lets you audit Azure Monitor workspace consumption — identify unused metrics and right-size ingestion this quarter; no forced deadline but directly actionable for cost and hygiene.
- CI/CD — Skip
- Leader — Learn: Adds visibility into Azure Monitor spend patterns, useful context for FinOps reviews, but no strategic decision is forced by this release.
- Signals: GA announcement
- Platform/SRE — Plan: If you have automation or multiple admins modifying IAM Identity Center users/groups (via SCIM, AD sync, or API), adopt the new Revision parameter on update/delete calls to prevent silent overwrites; no deadline, but worth scheduling for any identity-management automation this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: CloudWatch Omni is now GA in more regions including major global hubs; platform teams running multi-region or multi-cloud observability stacks should evaluate adopting it as a replacement or complement to their existing Prometheus/Grafana/OpenTelemetry pipeline this quarter.
- CI/CD — Skip
- Leader — Learn: CloudWatch Omni’s AI-powered, multi-cloud observability experience with SSO and agent observability support is worth tracking as it matures — no immediate strategic decision required, but relevant context for future build-vs-buy reviews of the observability stack.
- Platform/SRE — Plan: CVE-2026-78669 affects Terraform’s HTTP/2 stack but is not KEV-listed (EPSS 0.01) and requires a compromised provider/module registry to exploit; schedule an upgrade to 1.16.6 in the next routine Terraform maintenance window.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found) · CVE-2026-78669 — CISA KEV: not listed, EPSS 0.01
- Platform/SRE — Plan: Two correctness fixes worth scheduling: the env edit/set/rm overwriting bug could silently discard environment changes in Pulumi-managed stacks, and the drift status fix improves reliability reporting accuracy. No deadline, but upgrade when next maintaining the Pulumi toolchain.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Upgrade OpenTofu to v1.12.8 to address a CPU exhaustion vulnerability reachable via attacker-controlled HTTP/2 servers during
tofu init; no KEV listing or active exploitation reported, so no hard deadline, but schedule patching this sprint. - CI/CD — Plan: If pipelines run
tofu initagainst untrusted or external registries, upgrade to v1.12.8 to close the HTTP/2 CPU exhaustion vector; no confirmed exploitation or pipeline-breaking deadline, so plan within current cycle. - Leader — Skip
- Platform/SRE — Plan: Three containerd security fixes ship in this patch: two crash-on-pull vectors and a disk-exhaustion flaw (GHSA-hc94-p972-ch66) that could drain host storage on malicious image pulls. None are KEV-listed or actively exploited, but any team running Docker Engine or raw containerd in production should schedule an upgrade to 29.9.1 this sprint.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-95839 — CISA KEV: not listed, EPSS n/a, reported by 2 collected sources
- Platform/SRE — Plan: Four CVEs patched (including IAM/SCIM and OAuth2 fixes), none KEV-listed and EPSS scores are effectively zero — no active exploitation, but Grafana is standard in the observability stack; schedule an upgrade to 13.2.4 this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-15577 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-33374 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-92539 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Grafana sits in most Platform teams’ observability stack; this patch fixes four CVEs (including an IAM/SCIM Enterprise fix), but none are KEV-listed and EPSS scores are near zero — no active exploitation confirmed. Schedule an upgrade to 13.1.8 this sprint rather than treating it as an emergency.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-15577 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-33374 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-92539 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Four CVEs fixed including OAuth2 header leakage and an IAM/SCIM endpoint flaw; none are KEV-listed and EPSS scores are near zero, so no active exploitation anchor, but teams running Grafana 13.x in production should schedule an upgrade to 13.0.11 this sprint.
- CI/CD — Skip
- Leader — Skip
- Signals: major release (13.0) · CVE-2026-15577 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-33374 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-92539 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: v1.40.0 changes mcp_router to stop forwarding downstream headers (including
authorization) to backends by default — a silent auth-breakage risk on upgrade. Audit MCP router configs and validate header_forwarding settings before rolling this out to any cluster. - CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: CVE-2026-95839 is a security fix in the container runtime underlying every Kubernetes node, but it is not KEV-listed and carries no public exploitation signal, so this does not meet the Act bar. Plan to upgrade containerd to 2.4.2 across node pools this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: containerd 2.4 EOL 2027-05-16 · CVE-2026-95839 — CISA KEV: not listed, EPSS n/a, reported by 2 collected sources
- Platform/SRE — Plan: CVE-2026-95839 is not KEV-listed and no active exploitation is reported, but this patch hardens symlink handling, seccomp socket allowlisting, and image reference validation in the container runtime — all within the production-critical containerd path. Schedule an upgrade to 2.3.7 across node pools within your next maintenance window; containerd 2.3 EOL is 2028-04-30, so no forced-upgrade urgency.
- CI/CD — Skip
- Leader — Skip
- Signals: containerd 2.3 EOL 2028-04-30 · CVE-2026-95839 — CISA KEV: not listed, EPSS n/a, reported by 2 collected sources
- Platform/SRE — Plan: This open-source module automates ephemeral, auto-scaling GitHub Actions runner fleets on AWS via Terraform — worth evaluating if the org self-hosts runners on EKS or EC2 and wants to reduce idle capacity costs.
- CI/CD — Plan: Teams running self-hosted GitHub Actions runners on AWS should evaluate this module to gain on-demand ephemeral runners and eliminate persistent runner maintenance overhead; no deadline, but a useful near-term adoption candidate.
- Leader — Skip
- Platform/SRE — Learn: Oracle’s adoption of OpenTofu adds credibility to the fork as a production-grade Terraform alternative, reinforcing the case for teams still evaluating their IaC path after HashiCorp’s BSL relicensing — but no deadline or forced action exists here.
- CI/CD — Skip
- Leader — Plan: A major cloud vendor publicly standardizing on OpenTofu is a meaningful market signal; if your org hasn’t yet resolved its Terraform-vs-OpenTofu strategy following the 2023 BSL license change, schedule that evaluation this quarter before toolchain drift makes migration harder.
- Platform/SRE — Plan: Infrastructure automation (Terraform module fetches, Helm chart pulls, init containers) that clones public GitHub repos over unauthenticated HTTPS could intermittently fail; audit and add GitHub credentials to affected workflows.
- CI/CD — Plan: Pipelines cloning public GitHub repos over unauthenticated HTTPS risk intermittent checkout failures; audit all pipeline steps using unauthenticated HTTPS and switch to authenticated HTTPS (GITHUB_TOKEN) or SSH to ensure reliability.
- Leader — Skip
- Platform/SRE — Plan: Two items worth acting on this quarter: enable graceful shutdown on production Compute Engine instances where long-running tasks risk data loss on stop/delete, and review the Cloud Armor WAF v33-stable and v3.0-stable ruleset changes to assess whether updated detection rules alter behavior for existing tuned deployments.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: October 19, 2026 · GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: Teams running CodeQL on Swift projects will need to update their scanning configuration when adopting macOS 27 or Xcode 27 runners, as Apple has removed Intel x86_64 code from system binaries CodeQL depends on for build tracing. No forced deadline, but plan this alongside any macOS 27 runner migration.
- Leader — Skip
- Platform/SRE — Plan: GuardDuty Runtime Monitoring now supports 50+ tunable detection rules for EC2, EKS, and ECS workloads, covering MITRE ATT&CK tactics like persistence and privilege escalation. Evaluate and enable relevant rules this quarter, using dry-run mode first to reduce false positives before going live.
- CI/CD — Skip
- Leader — Learn: AWS expanding GuardDuty’s runtime threat detection with granular, MITRE-mapped rules signals a maturing managed-security posture for AWS-native environments; useful context when assessing build-vs-buy decisions around runtime security tooling.
- Platform/SRE — Skip
- CI/CD — Plan: The Xcode 27 hosted runner is now GA on GitHub Actions after public preview; if your team builds or tests Apple platform apps, schedule adoption to stay on current toolchain and avoid future runner deprecations.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: If your org operates in GovCloud or any of the newly supported commercial regions, this GA feature lets you centralize logs across accounts via AWS Organizations without custom pipelines — worth adding to your observability architecture this quarter.
- CI/CD — Skip
- Leader — Learn: Cross-account log centralization is now available in GovCloud, which matters for regulated-industry customers; free for one copy, $0.05/GB beyond that — useful context for FinOps and compliance conversations but no immediate decision required.
- Platform/SRE — Plan: If you run Oracle Database@AWS, this new GA capability lets you advertise a single aggregate CIDR or default route (0.0.0.0/0) over ODB peering instead of managing per-network entries — worth updating your ODB network peering config during your next network ops review cycle.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: GitLab Secrets Manager is now GA in 19.5 Premium/Ultimate, built on OpenBao — evaluate whether it can replace a standalone Vault deployment for GitLab-centric orgs, since it reuses the existing GitLab permission model and eliminates the sync-drift problem between vault access and project membership.
- CI/CD — Plan: Now GA in GitLab 19.5 — schedule evaluation of Secrets Manager as a replacement for unscoped CI/CD variables; it scopes credentials to individual jobs and attaches pipeline and job IDs to every credential read, making this a concrete supply-chain hardening step for GitLab-hosted pipelines.
- Leader — Learn: For orgs standardized on GitLab, this GA release shifts the build-vs-buy calculus on maintaining a separate secrets vault; no urgent vendor or licensing decision, but worth tracking as a potential toolchain consolidation as the feature matures on Dedicated.
- Signals: GitLab 19.5 EOL 2027-01-21 · GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: The GitLab MCP server is now GA with 19.5, letting MCP-compatible agents drive merge requests, pipelines, and work items under existing GitLab permissions. Evaluate integrating it into agentic pipeline automation workflows this quarter.
- Leader — Learn: GA availability of GitLab’s MCP server signals maturing AI-agent integration across the software development lifecycle; useful input when assessing whether to deepen or broaden AI tooling investment in the platform strategy.
- Signals: GitLab 19.5 EOL 2027-01-21 · GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: Code Review Flow is now GA on GitLab Duo Agent Platform, adding policy-enforced AI review as a merge gate tied to approvals, code owners, and security findings. Evaluate enabling it on GitLab pipelines if your org has rising AI-generated code volume; note the $0.25/review cost model before rolling out org-wide.
- Leader — Learn: GitLab’s GA of policy-governed AI code review introduces a per-review cost model ($0.25/review) and positions automated review as a platform control, not just a developer aid — worth tracking as a pattern for how AI-in-delivery scales and what it costs at volume.
- Signals: GA announcement
- Platform/SRE — Plan: Teams running self-hosted GitLab should schedule an upgrade to 19.5; the EOL signal (2027-01-21) confirms this is the current supported target — review release notes for any breaking changes or infra-side migration steps before upgrading.
- CI/CD — Learn: A new GitLab minor release may include pipeline, runner, or CI/CD workflow improvements worth evaluating — review the 19.5 changelog for any relevant build or deployment features, but no concrete deadline or breaking pipeline change is signaled.
- Leader — Skip
- Signals: GitLab 19.5 EOL 2027-01-21
- Platform/SRE — Skip
- CI/CD — Plan: New GA GitHub Enterprise Cloud feature enables ruleset-based OSS license checks in pipelines; schedule evaluation to enforce centralized license policy as a supply-chain hardening step this quarter.
- Leader — Plan: GA tooling for enforcing OSS license policy at scale on GitHub Enterprise Cloud directly addresses legal/compliance risk from dependency licensing; evaluate enabling it as a formal org standard this planning cycle.
- Signals: GA announcement
- Platform/SRE — Plan: New Docker 29 installs default to the containerd image store, which has different behavior for image layering, multi-platform support, and tooling compatibility; review and test before rolling out Docker 29 on new nodes or golden AMIs to avoid unexpected differences from existing hosts still on the legacy store.
- CI/CD — Plan: Any CI runner provisioning that installs Docker 29 fresh will get the containerd image store by default, which may affect build caching behavior and image layer handling; audit runner provisioning scripts and validate build pipelines against Docker 29 before upgrading runner images.
- Leader — Skip
- Platform/SRE — Plan: If your org has IPv6 compliance or architecture requirements, you can now route IPv6 traffic end-to-end through CloudFront to private ALB/NLB/EC2 origins without exposing them publicly. Evaluate updating VPC origin configs to dual-stack in your next architecture review.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA Azure VMSS capability that passively redistributes VM instances across availability zones to prevent zonal skew; assess whether existing VMSS deployments should enable it this quarter to improve resilience without manual rebalancing.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: New GA capability enabling precision time on Gen8/Gen9 instance families via Precision Time Placement Groups; evaluate PTPG adoption this quarter for distributed workloads requiring ordered event sequencing or accurate one-way latency measurement.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If your team runs Grafana Cloud with Adaptive Metrics, this new GA cost-first auto-apply mode can reduce active series counts without manual review — evaluate enabling it this quarter to lower observability ingestion costs.
- CI/CD — Skip
- Leader — Learn: Grafana’s cost-first auto-apply is a concrete example of automated FinOps tooling for observability spend — useful framing if you’re evaluating how to manage metrics cardinality costs at scale, but no leadership decision required.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: GitHub’s AI Scan for PRs is now GA, extending code vulnerability detection to languages and frameworks CodeQL doesn’t cover — evaluate enabling it in your GitHub Actions workflows this quarter to broaden supply-chain security coverage.
- Leader — Plan: GA availability makes this worth adding to your security standards: assess whether to mandate AI Scan alongside CodeQL as part of the org’s golden-path security policy for pull requests.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: This GA feature can automatically remediate code scanning alerts within your GitHub workflows, reducing manual triage burden. Evaluate enabling it on repositories that use GitHub Advanced Security to tighten the security feedback loop in your pipelines.
- Leader — Learn: GitHub’s agentic autofix moves automated security remediation from a developer convenience into a pipeline-integrated capability, which could reshape how teams handle vulnerability backlog — worth tracking as AI-driven developer tooling matures, but no immediate strategic decision is required.
- Signals: GA announcement
- Platform/SRE — Plan: New GA CloudWatch Pipelines capabilities let you split log streams by severity, source, or type into separate log groups with distinct retention and access controls, and apply sequential parsers to nested formats. Worth evaluating this quarter if you’re using CloudWatch Pipelines or considering consolidating log routing into a managed service.
- CI/CD — Skip
- Leader — Learn: This GA capability improves CloudWatch’s log-routing sophistication and could reduce observability costs via targeted retention policies, but it doesn’t change vendor risk, licensing, or require a strategic decision now.
- Signals: GA announcement
- Platform/SRE — Plan: If you manage ARC-enabled VMware or physical Windows servers, evaluate adding ASR for disaster recovery coverage this quarter — this closes a gap for hybrid infrastructure protection.
- CI/CD — Skip
- Leader — Learn: ASR support for ARC-managed on-premise workloads expands Azure’s hybrid DR story; worth noting if the org is evaluating or expanding ARC adoption for governance of on-premise fleets.
- Signals: GA announcement
- Platform/SRE — Plan: GA hardware-level audit logging for Azure Cloud HSM is a concrete compliance and forensic capability; orgs using HSM for key management should schedule enablement and integrate log feeds into their SIEM/observability pipeline this quarter.
- CI/CD — Skip
- Leader — Learn: Informs compliance posture for regulated environments relying on Azure Cloud HSM, but introduces no licensing, pricing, or vendor-risk change that requires a leadership decision now.
- Signals: GA announcement
- Platform/SRE — Plan: If you run Transfer Family SFTP servers, evaluate migrating host keys to Secrets Manager this quarter to simplify cross-region failover and server migrations without requiring clients to re-trust new host keys.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA capability lets teams upgrade EC2 Ubuntu LTS fleets to Ubuntu Pro in-place via License Manager without AMI rebuilds, unlocking 10-year patch coverage and Kernel Livepatch. Worth evaluating this quarter if running Ubuntu LTS instances with compliance or extended-support requirements.
- CI/CD — Skip
- Leader — Learn: Simplifies the path to Ubuntu Pro subscriptions for EC2 fleets, which can reduce compliance risk and extend OS support windows at a Marketplace-managed cost; no forced decision, but relevant context for Ubuntu fleet licensing strategy.
- Platform/SRE — Plan: If your platform runs multi-step or agentic Lambda workflows, the 30,000 operation limit and 1 MB checkpoint open up architectures previously blocked by quota; evaluate whether existing workflows hitting the old 3,000-op ceiling should be redesigned to take advantage.
- CI/CD — Skip
- Leader — Learn: The expanded limits make Lambda durable functions more viable for long-running agentic AI orchestration, worth tracking if your org is evaluating serverless vs. container-based workflow engines for AI workloads.
- Platform/SRE — Plan: The new service quota parity checks and wait-for-target-group-health blocks directly address common multi-region failover failure modes; platform teams using ARC Region switch should evaluate updating their recovery plans to incorporate these execution blocks this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run RDS for SQL Server 2022, you can now add RDS Proxy to gain connection pooling and up to 83% faster Multi-AZ failover with preserved app connections; evaluate whether to enable this for existing SQL Server 2022 instances this quarter.
- CI/CD — Skip
- Leader — Learn: RDS Proxy now covers SQL Server 2022, expanding HA and connection-pooling options for SQL Server workloads on AWS; no strategic or cost decision required, but worth noting for future SQL Server architecture reviews.
- Platform/SRE — Plan: If your platform automation still uses classic PATs for GitHub API access, schedule a migration to fine-grained GitHub Apps tokens this quarter — fewer broad credentials reduces blast radius from a compromised token.
- CI/CD — Plan: Pipelines relying on classic PATs for repo access or triggering workflows should be migrated to GitHub Apps with scoped permissions; no hard deadline, but this hardening step fits a Q4 supply-chain hygiene project.
- Leader — Skip
- 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 — Skip
- CI/CD — Plan: Verify your repositories have push protection enabled and audit any existing Anthropic API keys or Salesforce credentials in build logs or secrets; no deadline but this is a worthwhile supply-chain hardening step to schedule.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: If your org runs internal package mirrors accessible without credentials, configure the new Anonymous auth method at the org level to simplify Dependabot registry setup and reduce credential management overhead.
- Leader — Skip
- Platform/SRE — Plan: This GA capability changes how serverless web apps can be architected on AWS — Lambda Web Functions can now sit behind CloudFront for edge TLS, caching, DDoS protection, and WAF, with OAC locking down direct access. Worth evaluating for teams running Lambda-based web workloads this quarter.
- CI/CD — Skip
- Leader — Learn: New AWS capability that shifts the serverless-plus-CDN architecture picture — Lambda Web Functions are now a first-class CloudFront origin — but no pricing change, licensing impact, or forced migration means no decision is pending.
- Platform/SRE — Plan: New GA capability worth evaluating this quarter for any workloads using Databricks or Twilio: eliminates custom rotation Lambda functions and ensures applications pick up rotated credentials automatically without code changes.
- CI/CD — Learn: Relevant if pipelines consume Databricks personal access tokens or Twilio API keys, but there is no deadline or pipeline breakage — file as a pattern to consider when next reviewing how build credentials are rotated.
- Leader — Skip
- Platform/SRE — Learn: New GA AWS Lambda primitive supporting direct HTTP handling (Express/Hono, no adapters) with a different billing model; worth tracking for future platform architecture patterns, but no existing infrastructure needs changing and existing Lambda Event Functions require no migration.
- CI/CD — Skip
- Leader — Plan: The active-CPU billing model (vs. idle CPU) could meaningfully reduce Lambda costs for I/O-bound workloads; evaluate this as a golden-path serverless option and assess cost-optimization potential against current Lambda spend this planning cycle.
- Platform/SRE — Plan: This GA minor release patches a snapshot integrity error and restores elided asset contents from prior state — real correctness bugs for teams running Pulumi in production. Schedule an upgrade within the current planning cycle; no hard deadline exists.
- CI/CD — Learn: The new automation API methods (version, whoami, install) across Node/Python/Go SDKs expand programmatic pipeline control options, but no deprecation or breaking change makes this actionable today.
- Leader — Skip
- Platform/SRE — Plan: If you use pulumi-java with Maven 3.10, plugin downloads are silently broken because Maven 3.10 mixes log output into stdout and corrupts JSON parsing; upgrade to Pulumi SDK v3.268.0 to restore correct behavior while the upstream Maven bug is resolved.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Four HTTP/2 CVEs in the Docker daemon (daemon crash, memory exhaustion, flow-control bypass, CPU spike) are fixed in this release; none are KEV-listed and EPSS scores are near zero, so no active exploitation clock, but schedule an upgrade to v29.9.0 if running Docker Engine on cluster nodes or VM fleets.
- CI/CD — Plan: If Docker-in-Docker or a Docker socket is part of your build runners, the same HTTP/2 daemon vulnerabilities apply; plan to update the Docker Engine version in runner images or host provisioning to v29.9.0, no hard deadline but meaningful DoS risk in shared build infrastructure.
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found) · CVE-2026-56857 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-78659 — CISA KEV: not listed, EPSS 0.01 · CVE-2026-78663 — CISA KEV: not listed, EPSS 0.01
- Platform/SRE — Plan: Two GHSA-tracked crash vulnerabilities in the oauth2 and api_key_auth filters (triggered by CONNECT requests lacking a :path header) are patched in 1.39.3; no KEV listing or active exploitation reported, but operators using either filter should schedule the patch within the current sprint. Envoy 1.39 is supported until 2027-07-14.
- CI/CD — Skip
- Leader — Skip
- Signals: Envoy 1.39 EOL 2027-07-14
- Platform/SRE — Plan: Upgrade Envoy 1.38.x to 1.38.7 this quarter: it fixes a non-KEV/EPSS-0.00 CVE in wasmtime, several worker-thread race conditions during RDS route-config updates, and a 1.38.0-introduced regression that underreported Prometheus native histogram quantiles. No hard deadline; 1.38 EOL is 2027-04-23.
- CI/CD — Skip
- Leader — Skip
- Signals: Envoy 1.38 EOL 2027-04-23 · CVE-2026-54786 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Two crash-inducing security fixes (GHSA-8vc2-jrm4-835w, GHSA-47vj-9r25-wv5j) affect Envoy’s oauth2 and api_key_auth filters when handling CONNECT requests; no KEV listing or active exploitation reported, so schedule an upgrade to 1.38.6 this sprint if either filter is in use.
- CI/CD — Skip
- Leader — Skip
- Signals: Envoy 1.38 EOL 2027-04-23
- Platform/SRE — Plan: Patch Envoy to 1.37.9 this quarter to resolve CVE-2026-54786 (not KEV-listed, EPSS 0.00) and three worker-thread race conditions in AWS request signing, local rate limiting, and SDS secret handling that could cause instability under RDS route updates; no forced deadline, 1.37 EOL is 2027-01-13.
- CI/CD — Skip
- Leader — Skip
- Signals: Envoy 1.37 EOL 2027-01-13 · CVE-2026-54786 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Two GHSA-classified crash vulnerabilities in Envoy’s oauth2 and api_key_auth filters can be triggered by CONNECT requests; no KEV listing or active exploitation reported, but any team running these filters in production should schedule an upgrade to v1.37.8 this sprint. Envoy 1.37 EOL is 2027-01-13, so the branch is still supported.
- CI/CD — Skip
- Leader — Skip
- Signals: Envoy 1.37 EOL 2027-01-13
- Platform/SRE — Plan: Four CRITICAL CVEs patched — including RCE via Kustomize remote refs and Jsonnet imports in the repo-server, plus an AppProject restriction bypass — with no KEV listing or confirmed active exploitation. Schedule upgrade to v3.4.10 this sprint; none of the exploits have a forced deadline, but CRITICAL severity in a GitOps control plane warrants prompt action.
- CI/CD — Plan: The HIGH-severity command injection via SSH Git repository proxy URL (CVE-2026-55797) and the AppProject hook bypass directly affect the deploy path managed through Argo CD. No active exploitation is confirmed, but teams running Argo CD for GitOps deployments should plan an upgrade to v3.4.10 before end of current sprint.
- Leader — Skip
- Signals: Argo CD 3.4 supported · CVE-2025-61560 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-55797 — CISA KEV: not listed, EPSS 0.02 · CVE-2026-77459 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Four CRITICAL-severity vulnerabilities patched, including repo-server command execution via Kustomize and AppProject restriction bypass — none are KEV-listed and EPSS scores are near zero, so no confirmed exploitation, but schedule upgrade of Argo CD to v3.3.15 this sprint given the RCE class of findings.
- CI/CD — Plan: Argo CD v3.3.15 patches CRITICAL command-execution flaws in the GitOps deployment tool; coordinate with the platform team to schedule a cluster upgrade to v3.3.15, prioritizing any environments where untrusted Kustomize or Jsonnet sources are in use.
- Leader — Skip
- Signals: Argo CD 3.3 supported · CVE-2025-61560 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-55797 — CISA KEV: not listed, EPSS 0.02 · CVE-2026-77459 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Argo CD 3.5.4 fixes four CRITICAL CVEs including arbitrary command execution in the repo-server via Kustomize and Jsonnet, plus an AppProject restriction bypass. None are KEV-listed and EPSS is very low, but CRITICAL severity in a core GitOps component warrants patching this sprint — upgrade clusters to 3.5.4 promptly.
- CI/CD — Plan: The CRITICAL command-injection paths (Kustomize remote refs, Helm home, Jsonnet imports) run inside the repo-server that processes your GitOps manifests, making this directly relevant to the deploy path. Schedule an upgrade to 3.5.4; no active exploitation confirmed yet but the attack surface is in build artifact processing.
- Leader — Skip
- Signals: Argo CD 3.5 supported · CVE-2025-61560 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-55797 — CISA KEV: not listed, EPSS 0.02 · CVE-2026-77459 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Critical patch releases in GitLab warrant upgrading if you self-host; review CVE details in the release notes and schedule the upgrade to the applicable branch (19.4.2, 19.3.4, or 19.2.8) this sprint. No exploitation confirmed in signals, so Act ceiling is not reached.
- CI/CD — Plan: If GitLab CI is your pipeline platform and you run a self-managed instance, plan an upgrade to the patched version matching your branch; critical patches can affect runner availability and API stability. No hard deadline or active exploitation in signals.
- Leader — Skip
- Platform/SRE — Plan: Regex matchers in Application Load Balancer URL maps are now GA, enabling more precise traffic routing via RE2 syntax on paths, headers, and query params — evaluate adopting this for routing rules this quarter.
- CI/CD — Plan: Cloud Build now lets you pin builds to a release channel controlling how often the underlying Debian and Docker versions are updated — review your build configs and private pools to choose an appropriate channel for reproducibility.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: If any Docker Hub personal accounts were converted to organizations in your org, PATs used for image pulls in infrastructure tooling may have been re-assigned to unintended owners. Audit and rotate affected Docker Hub PATs; no hard deadline but treat as a near-term security hygiene task.
- CI/CD — Plan: Docker Hub PATs are widely embedded in CI/CD pipelines for registry auth; if any team converted a personal Docker Hub account to an org, those tokens may have changed hands. Identify any converted accounts and rotate all associated PATs in pipeline secrets before they can be leveraged.
- Leader — Skip
- Signals: CVE-2026-105445 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: A new GA CloudWatch dashboard surfacing OTel metrics (memory, network, latency, keyspace, errors) for Valkey node clusters — worth scheduling adoption to consolidate cache observability; note that detailed 15-second metrics incur standard CloudWatch OTel pricing.
- CI/CD — Skip
- Leader — Learn: AWS now bundles a pre-built observability layer for ElastiCache Valkey at no additional platform cost (standard CloudWatch OTel pricing applies for enhanced polling), relevant context if the org is evaluating its caching observability spend.
- Platform/SRE — Plan: If you run Azure Arc-enabled Kubernetes clusters, plan migration from the Azure Key Vault Secrets Provider Extension to the Azure Key Vault Secret Store Extension before the hard retirement date of October 9, 2027. One year is enough runway to schedule the migration, but start scoping which clusters are affected now.
- CI/CD — Skip
- Leader — Plan: Azure is retiring a secrets-integration extension for Arc-enabled Kubernetes with a clear replacement in the same ecosystem; ensure teams using Arc clusters have this migration on their roadmap before October 9, 2027, as there is no stay-on-current option beyond that date.
- Signals: deprecation/EOL deadline mentioned: October 9, 2027
- Platform/SRE — Plan: New GA capability for Aurora PostgreSQL and RDS for PostgreSQL that detects post-credential-compromise data exfiltration and destruction with no agent or config changes required; platform teams running RDS/Aurora should evaluate enabling the add-on for their organization this quarter via the GuardDuty console or CloudFormation.
- CI/CD — Skip
- Leader — Learn: GuardDuty now extends RDS threat detection beyond login anomalies to query-pattern behavior using ML, relevant for understanding current AWS-native security coverage breadth — no strategic decision or policy change is immediately required.
- Platform/SRE — Plan: GA feature worth adopting for teams using AWS Network Firewall with EKS/ECS — wildcard patterns like app=payments-* can replace per-variant rules, reducing rule sprawl in dynamic container environments. Evaluate and consolidate existing container attribute rules this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: New GA billing dimension adds model, provider, and inference-type breakdowns for Bedrock spend in Cost Explorer and Budgets — useful context for teams managing cloud cost allocation, but no operational infrastructure change required.
- CI/CD — Skip
- Leader — Plan: If your org runs Bedrock workloads, configure Bedrock product attribute dimensions in Cost Explorer and Budgets this quarter to gain per-model and per-provider spend visibility — enables tighter budget guardrails and informs model-selection trade-offs.
- Platform/SRE — Plan: New GA instance type offering 30% better compute than Graviton3 and higher EBS bandwidth (up to 300 Gbps / 1.6M IOPS) is worth evaluating this quarter for EBS-bound workloads like high-performance file systems; no forced migration, just an adoption decision.
- CI/CD — Skip
- Leader — Learn: Graviton4-based C8gb instances improve the performance-per-dollar profile for compute and storage-intensive workloads, useful background for future FinOps or Graviton migration conversations, but no strategic decision is forced now.
- Signals: GA announcement
- Platform/SRE — Plan: StandardV2 is now the default managed NAT Gateway SKU for new AKS clusters in supported regions, which may affect cluster provisioning templates and IaC modules. Review and update cluster-creation configurations to account for the new default SKU before spinning up new clusters.
- CI/CD — Skip
- Leader — Learn: AKS now manages a higher-performance NAT Gateway SKU by default for new clusters, shifting the networking default without a licensing or cost-model change — worth noting as AKS managed networking capabilities mature.
- Signals: GA announcement
- Platform/SRE — Plan: If your team uses CDKTF for infrastructure, this HN discussion signals potential direction changes worth tracking; no concrete EOL date means no Act, but evaluate whether to continue investing in CDKTF vs. native HCL or OpenTofu-based workflows this quarter.
- CI/CD — Skip
- Leader — Plan: A high-signal HN thread (136 pts, 134 comments) on CDKTF’s future warrants a toolchain-risk review if your org has standardized on it — especially given the HashiCorp/IBM acquisition context; assess alternatives before teams invest further.
- Platform/SRE — Plan: If you operate multiple OpenTelemetry Collector deployments, this GA release enables centralized config management via OpAMP without migrating to Grafana Alloy first — worth evaluating this quarter as a way to reduce config drift across collector fleets.
- CI/CD — Skip
- Leader — Learn: Grafana’s GA of OpAMP-based fleet management signals a maturing centralized-observability management model worth tracking if your org is standardizing on OpenTelemetry — no decision required now but relevant to future platform strategy.
- Signals: GA announcement
- Platform/SRE — Plan: GitLab 19.4 reaches EOL on 2026-12-17 (70 days); if self-hosting on 19.4, schedule an upgrade to a supported minor now. The featured security dashboard is beta-only and should not factor into upgrade timing.
- CI/CD — Skip
- Leader — Learn: Centralized org-wide risk scoring that incorporates KEV and EPSS across all top-level groups is a meaningful step for security program governance and auditor readiness, but the feature is currently in beta for GitLab.com only — no adoption decision warranted yet.
- Signals: GitLab 19.4 reaches EOL in 70d (2026-12-17)
- Platform/SRE — Learn: Improved secret detection in GitHub repositories is a useful security capability, but it has no operational change or deadline for infrastructure teams to act on.
- CI/CD — Plan: Evaluate enabling the new context-aware secret scanning model in GitHub Advanced Security to strengthen supply-chain hygiene; no hard deadline, but worth scheduling as part of a supply-chain hardening quarter.
- Leader — Learn: GitHub’s investment in AI-driven secret detection signals maturing supply-chain security tooling, worth factoring into security posture reviews, but no pricing, licensing, or strategic decision is triggered.
- Platform/SRE — Plan: If ‘record all resource types’ is enabled, these 77 types—including EC2, GuardDuty, Inspector, and S3—will be tracked automatically, which quietly expands coverage and may increase Config costs. Review the new type list against your compliance rules and cost baseline this quarter.
- CI/CD — Skip
- Leader — Skip
- 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 — Plan: Cloud SDK 588.0.0 has already removed the managed-flink-client component; audit any gcloud automation or IaC scripts that invoke it and update them before upgrading the SDK in your environment.
- CI/CD — Plan: If CI runners auto-update gcloud, pipelines using managed-flink-client commands will break on Cloud SDK 588.0.0; audit build scripts now and pin the SDK version or remove the dependency before runners pull this release.
- Leader — Skip
- Signals: GA announcement · breaking-change flagged
- Platform/SRE — Plan: Teams running AWS Batch workloads can now replace custom metric scrapers with native CloudWatch metrics covering queue health, failure rates, and state-transition durations; worth integrating into existing dashboards and alerting this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: The pod name dimension on AKS platform metrics (kube_pod_status_phase and related) is being removed September 30, 2027; audit Azure Monitor dashboards and alerts that rely on per-pod granularity from these metrics and plan migration to aggregate counters or Prometheus-based alternatives before that date.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: September 30, 2027
- Platform/SRE — Plan: New GA capability to restrict Identity Store and SCIM API access by VPC endpoint or IP allowlist; evaluate enforcing VPC-endpoint-only access for the Identity Store API as part of your AWS SSO hardening roadmap this quarter.
- CI/CD — Skip
- Leader — Learn: AWS now allows network-level perimeter controls around the APIs that manage SSO users and groups; worth noting as an available hardening option when setting identity-security standards across accounts.
- Platform/SRE — Plan: Teams running AFT for multi-account provisioning should evaluate upgrading to AFT 1.22.0 to enable plan-only runs, which support pre-rollout drift detection and safer customization validation; no hard deadline, but it’s a meaningful operational improvement worth scheduling this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run AWS Batch compute environments on EKS, you can now migrate from the aws-auth ConfigMap to the newer access entry API for IAM-principal authentication; schedule an UpdateComputeEnvironment pass to set accessEntry.desiredState=ENABLED, simplifying auth lifecycle management on those clusters.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you manage shared AMIs across accounts or organizations, this new GA feature can replace any custom tag-replication automation you’ve built; evaluate adopting the ’ec2:SharedTag/’ prefix pattern this quarter to simplify your cross-account AMI workflows.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA capability keeps ACME cert issuance traffic inside the AWS network via a VPC interface endpoint; worth scheduling adoption this quarter for compliance-sensitive or egress-restricted environments that already use ACM with ACME clients.
- CI/CD — Skip
- Leader — Learn: ACM now offers a private network path for certificate issuance, which strengthens the compliance and network-isolation story for regulated workloads; no strategic decision or cost change is forced by this GA addition.
- Platform/SRE — Plan: Prometheus 3.13.4 patches a gRPC HTTP/2 memory-exhaustion vulnerability (GO-2026-6348) and fixes federation corruption of float native histograms — schedule an upgrade to 3.13.4 this sprint for any federated Prometheus deployment.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Upgrade OpenTofu to v1.12.7 to address CVE-2026-78662 and CVE-2026-56855, which allow an attacker-controlled SSH server to deadlock remote-exec/file provisioner connections; neither CVE is KEV-listed and EPSS scores are near zero, so schedule within the next IaC toolchain maintenance cycle rather than treating as an emergency.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-56855 — CISA KEV: not listed, EPSS 0.01 · CVE-2026-78662 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: GA IaC release with real breaking changes: WinRM provisioner removed, macOS 13 Ventura now minimum, and 1.13.x will be the last series supporting 32-bit CPUs — audit current usage of these before upgrading, and plan the 32-bit migration for the next cycle.
- CI/CD — Plan: If OpenTofu runs inside pipelines (infra provisioning steps), audit for WinRM provisioner usage and verify the base64gzip output change doesn’t break deterministic artifact checks before scheduling the upgrade.
- Leader — Learn: OpenTofu 1.13’s healthy GA cadence (new planning primitives, upcoming linting/policy experiment) reinforces confidence in the Terraform-alternative bet, but there is no licensing, pricing, or vendor-risk development requiring a leadership decision here.
- Signals: OpenTofu 1.13 EOL 2027-08-01 · deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: CVE-2026-17106 allows a crafted tar archive to write outside the extraction directory in the Docker engine — real exposure for any host running Moby/Docker, but not KEV-listed and EPSS is 0.00 with no active exploitation evidence. Schedule an upgrade to v25.0.18 this sprint rather than treating it as an emergency.
- CI/CD — Skip
- Leader — Skip
- Signals: major release (25.0) · CVE-2026-17106 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Skip
- CI/CD — Plan: Jenkins 2.580.1 carries a breaking-change flag; review the upgrade guide and schedule a controlled upgrade of your Jenkins controller before the change causes pipeline failures.
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: Grafana is a common observability-stack component; upgrade to 13.2.3 to remediate CVE-2026-13719, CVE-2026-13720, and CVE-2026-81841 — none are KEV-listed and all carry EPSS 0.00, so this is a scheduled patch, not an emergency.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-13719 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-13720 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-81841 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Upgrade Grafana to 13.1.7 to remediate CVE-2026-13719, CVE-2026-13720, and CVE-2026-81841; none are KEV-listed and all carry EPSS 0.00, so schedule the patch this sprint rather than treating it as an emergency response.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-13719 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-13720 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-81841 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: CVE-2026-35189 fixes a remote DoS in TLS certificate parsing via BoringSSL; not KEV-listed and EPSS is near-zero, so no evidence of active exploitation — schedule an upgrade to v1.39.2 this sprint rather than treating it as an emergency.
- CI/CD — Skip
- Leader — Skip
- Signals: Envoy 1.39 EOL 2027-07-14 · deprecation mentioned (no explicit date found) · CVE-2026-35189 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Kubernetes v1.34 GA swap support with NVMe backing is worth evaluating for memory-dense node pools this quarter; assess enabling swap on nodes running agentic AI or sandboxed workloads to reduce OOM kills and improve pod density without fleet-wide urgency.
- CI/CD — Learn: The benchmark covers CI/CD kernel build workloads as a validated use case, but enabling swap on nodes is a platform configuration decision — useful context for understanding build pod resource headroom if your CI runs on shared Kubernetes clusters.
- Leader — Plan: Up to 3× pod density on existing hardware is a material FinOps opportunity worth adding to the next infrastructure planning cycle; evaluate whether adopting Kubernetes v1.34 swap + NVMe changes the cost model for memory-intensive AI and build workloads in your standard platform stack.
- Signals: GA announcement
- Platform/SRE — Plan: If you operate AWS Private CA, the new IssueCertificateDetails CloudTrail management event (auto-delivered, no opt-in) enables compliance auditing and failed-issuance alerting that wasn’t possible before; schedule a review of your CloudTrail-based monitoring to add rules for this event, including pre-signing failures and algorithm tracking.
- CI/CD — Skip
- Leader — Skip
- 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 — Skip
- CI/CD — Plan: CI/CD pipelines can now trigger Copilot code reviews programmatically via API; evaluate integrating into PR automation workflows to enforce review coverage without manual steps.
- Leader — Skip
- Platform/SRE — Learn: Infrastructure automation using GitHub App tokens (e.g., Flux, Argo CD, Terraform GitHub provider) should still work without changes, but teams relying on token introspection or format-specific parsing should verify compatibility with the new stateless format.
- CI/CD — Plan: The rollout is complete, so all newly minted GitHub App installation tokens already use the stateless format; audit any pipeline code or tooling that parses or makes structural assumptions about token format to confirm nothing breaks.
- Leader — Skip
- Platform/SRE — Plan: New GA capability lets teams query ElastiCache Valkey metrics via PromQL in Grafana and CloudWatch, with optional 15-second granularity for catching short-lived latency spikes; schedule enablement of standard OTel metrics now (free) and evaluate detailed monitoring for critical clusters this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: This new GA feature provides a centralized, API-queryable view of EOL/end-of-support timelines for EKS, RDS, Lambda, and more — directly relevant to managing upgrade schedules before account-specific Planned Lifecycle Events fire. Plan to integrate the AWS Health API into operational runbooks and upgrade planning workflows this quarter, particularly for EKS version tracking.
- CI/CD — Skip
- Leader — Learn: This AWS feature enables proactive version governance across RDS, EKS, Lambda and more, which supports building org-wide upgrade standards and reducing reactive EOL scrambles; no immediate decision required, but worth factoring into platform governance policy discussions.
- Platform/SRE — Plan: Kubernetes 1.37 is now GA on EKS with notable promotions (Metrics API to GA as metrics.k8s.io/v1, DRA device taints to GA). Plan an upgrade evaluation this quarter; no forced-upgrade deadline exists yet, but staying current reduces future skew risk.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: GA capability that changes how ECS services using VPC Lattice handle progressive delivery — evaluate adopting native traffic-shifting to replace or simplify any existing CodeDeploy or manual canary setups this quarter.
- CI/CD — Plan: Native canary/linear deployment strategies with CloudWatch alarm rollback and lifecycle hooks are worth integrating into ECS deployment pipelines; evaluate replacing custom traffic-shifting logic with this managed approach.
- Leader — Skip
- Platform/SRE — Plan: New GA observability capability directly relevant to teams running Route 53 Resolver and DNS Firewall — plan to enable CloudWatch Metrics and Contributor Insights for DNS query visibility and anomaly alerting this quarter, noting that standard CloudWatch ingestion costs apply.
- CI/CD — Skip
- Leader — Learn: Incremental native observability addition to existing Route 53/CloudWatch stack; no strategic, licensing, or pricing-model change beyond standard CloudWatch usage costs — useful context for teams evaluating DNS security posture but no decision required.
- Platform/SRE — Skip
- CI/CD — Plan: Checks, workflow runs, and commit statuses are now subject to the same retention window as artifacts and logs. Audit your Actions retention setting to confirm build history is kept long enough to satisfy any compliance or audit trail requirements.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Learn: The ConfigPoisoning class — attacker-controlled execution via .git/config and .gitattributes — is worth understanding when hardening pipelines that clone external or untrusted repos; the specific exploit requires the DeepSeek-Reasonix desktop client, but GitLab notes multiple coding agents share the same root flaw.
- Leader — Plan: GitLab’s research found the ConfigPoisoning class affects multiple widely-used AI coding agents, not just DeepSeek-Reasonix; if the org is standardizing on AI coding assistants, add security vetting of approved tools to the golden-path policy before broad rollout.
- Signals: CVE-2026-102437 — CISA KEV: not listed, EPSS 0.01
- Platform/SRE — Plan: If you run DCsv3 or DCdsv3-series VMs in production, plan migration to a supported confidential compute series before October 31, 2029; the deadline is distant but inventory and migration scoping should enter the backlog now.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: October 31, 2029
- Platform/SRE — Plan: New GA capability worth evaluating this quarter: remediation plans surface root-cause groupings with Terraform and CloudFormation fix examples, making it practical to reduce Security Hub noise and address misconfigurations at the source rather than per-finding.
- CI/CD — Skip
- Leader — Learn: Security Hub’s new prioritized remediation plans expand AWS’s native security posture tooling at no extra cost — worth tracking as it may influence how teams standardize on AWS-native vs. third-party CSPM solutions.
- Platform/SRE — Plan: A new GA feature in Secrets Manager surfaces rotation gaps and encryption-key misconfigurations directly in the console at no extra cost; schedule a pass through your secrets inventory this quarter to act on flagged items before they become findings in a security review.
- CI/CD — Learn: Console-based recommendations don’t change how pipelines execute, but the rotation and key-management nudges are relevant context for teams auditing how pipeline secrets are stored in Secrets Manager.
- Leader — Learn: A free capability improvement to an existing standard-stack service; no pricing, licensing, or vendor-risk decision required, but worth noting as reinforcement for a secrets-rotation policy or security posture standard.
- Platform/SRE — Plan: If you operate in opt-in or GovCloud/China regions, evaluate enabling multi-Region IAM Identity Center replication this quarter to improve SSO resilience; requires setting up a multi-Region customer-managed KMS key for existing instances.
- CI/CD — Skip
- Leader — Learn: IAM Identity Center now supports identity replication across opt-in and GovCloud regions, a useful resilience capability to factor into multi-region access strategy and compliance planning.
- Platform/SRE — Plan: New GA capability lets Redshift query S3 tables in remote regions without replication, with enhanced VPC routing keeping traffic off public networks; evaluate for multi-region data lake architectures or compliance-sensitive workloads this quarter.
- CI/CD — Skip
- Leader — Learn: Relevant to orgs with data-residency or compliance constraints (financial, healthcare, government) — cross-region querying without replication simplifies global analytics architecture, but no strategic decision is forced by this announcement.
- Platform/SRE — Plan: Platform teams running Tempo 3.0 in microservices mode with Kafka-based ingestion shipped without TLS support — a real security gap. Upgrading to 3.1 closes it with TLS and additional SASL mechanisms (SCRAM-SHA-256/512, OAUTHBEARER, AWS_MSK_IAM); schedule the upgrade this quarter if Kafka ingestion is in use.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: New GA capability lets npm trusted publishing configs manage dist-tags (latest, next, beta promotion) with short-lived OIDC credentials instead of long-lived tokens — schedule adoption to reduce static secret exposure in publish workflows.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: The GA async merge API enables programmatic merge queue management and stacked PR workflows; evaluate adopting it to automate release orchestration or replace custom merge scripts.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Grafana 13.2 on AMG brings Git Sync (dashboards as code tied to a repo), dynamic dashboards, and PromQL support in the CloudWatch data source — plan an evaluation and workspace upgrade this quarter if you run AMG; 13.2 is supported until 2027-05-18.
- CI/CD — Skip
- Leader — Learn: Git Sync enabling dashboard-as-code and PromQL queries against CloudWatch OTLP metrics represent a meaningful shift in managed observability capabilities, worth factoring into platform tooling direction — but no strategic decision is required now.
- Signals: Grafana 13.2 EOL 2027-05-18 · GA announcement
- Platform/SRE — Plan: ARC runs on Kubernetes clusters you operate; the 0.15.0 improvements to runner scale-set reliability during cluster upgrades are worth evaluating and scheduling for adoption this quarter. No deadline or security fix in the signals.
- CI/CD — Plan: If you operate self-hosted GitHub Actions runners via ARC, 0.15.0 brings reliability and observability gains for large runner fleets — worth scheduling an upgrade to reduce disruption during runner or cluster maintenance windows.
- Leader — Skip
- Platform/SRE — Plan: New GA capability to enforce PANW DNS threat intelligence (C2, malware, phishing, newly registered domains) directly at the VPC DNS layer without deploying separate appliances — worth evaluating this quarter if the org has PANW licensing or wants to strengthen DNS egress controls across VPCs.
- CI/CD — Skip
- Leader — Learn: Signals a tighter AWS–Palo Alto integration for DNS security via License Manager and Firewall Manager; relevant background if the org already holds PANW licenses or is evaluating its DNS security vendor posture, but no decision is forced.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: New GA GitHub capability lets repository admins route Dependabot version and security update jobs to specific runner types, labels, or groups; worth evaluating if your org uses self-hosted runners and needs network isolation or resource controls for dependency update jobs.
- 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 — Plan: If on-prem Kafka migration to MSK is on the roadmap, evaluate AWS Transform’s new assessment agent this quarter — it automates topology mapping, compatibility checks, broker right-sizing, and cost projection that otherwise takes weeks.
- CI/CD — Skip
- Leader — Learn: This tool generates AI-assisted TCO business cases for Kafka-to-MSK migrations, which could inform a build-vs-buy or cloud-migration decision, but it doesn’t force one — useful context for orgs still running self-managed Kafka.
- Platform/SRE — Plan: Teams centralizing AWS networking with shared VPCs can now use a single DataSync VPC endpoint per central account instead of one per spoke account; evaluate consolidating existing per-account endpoints to reduce IP consumption and maintenance overhead this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: This simplifies multi-account automation at scale — teams managing SSM runbooks across an AWS organization can replace manual account-ID lists with OU/org-level RAM shares that auto-update as accounts join or leave. Worth adopting as part of your multi-account SSM document management strategy this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: GKE Standard’s GA increase to 512 pods per node (up from 256) doubles workload density but requires a /22 Pod CIDR block for nodes in the 257–512 range — evaluate whether your cluster IP address plan supports this before enabling denser node configurations.
- CI/CD — Skip
- Leader — Learn: GKE’s doubled pod-density ceiling may shift cluster sizing and cost economics for teams running dense workloads; the new X5 48TB memory tier is worth noting only if the org operates SAP HANA at scale and previously hit the 32TB single-node ceiling.
- Signals: GA announcement
- Platform/SRE — Plan: Workloads in private VPCs without internet egress can now verify JWTs via PrivateLink rather than requiring internet access; evaluate creating an interface VPC endpoint if you run air-gapped or restricted-egress VPCs that rely on IAM outbound identity federation.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: A new GA GitHub Enterprise Cloud governance control that tightens human access to sensitive org actions; no infrastructure change required, but worth understanding when designing access-control policies.
- CI/CD — Plan: Evaluate which release and deployment actions qualify as high-impact in your org and whether enabling proof-of-presence would require changes to release-approval workflows; no deadline, but this is a concrete supply-chain hardening step to schedule this quarter.
- Leader — Plan: Evaluate rolling out proof-of-presence as an org-wide GitHub Enterprise Cloud policy to reduce insider-threat and account-takeover risk on sensitive actions; no deadline, but a meaningful security governance improvement to bring into your next planning cycle.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: GitHub Copilot Business and Enterprise orgs have a 28-day window to review and adjust the new default-on policy for GA Copilot features before it takes effect; leaders should audit which features will be auto-enabled and confirm they align with data-handling and acceptable-use policies.
- Signals: GA announcement
- Platform/SRE — Plan: Teams running ElastiCache Global Datastore across regions can now enforce consistent IAM/SCP policies and cost allocation via tags; worth updating your tagging standards and IAM policies this quarter to close the permission-model gap.
- CI/CD — Skip
- Leader — Learn: This closes a cost-allocation and access-control gap in multi-region ElastiCache deployments, useful context if the org is standardizing FinOps tagging policies across AWS resources.
- Platform/SRE — Plan: New GA Azure capability enabling immediate disk restoration from application-consistent restore points on VMs with Premium v2 or Ultra data disks; evaluate adopting Instant Access in DR runbooks to reduce RTO for high-performance storage workloads.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Teams running Apigee hybrid on Kubernetes should schedule an upgrade to v1.15.8, which patches several security issues: JWT refresh token revocation, HTTP 103 Early Hints response desynchronization, JavaCallout policy, and SSRF in AI protection policies. No KEV listing or active exploitation reported, so no immediate emergency, but the Helm chart upgrade path is straightforward.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: A new GA EKS managed add-on that replaces round-robin LB with real-time GPU-signal-aware routing (KV cache, queue depth, LoRA residency) for HyperPod clusters — evaluate adopting this quarter if your team runs SageMaker HyperPod inference workloads on EKS.
- CI/CD — Skip
- Leader — Learn: AWS’s inference gateway pattern (single endpoint, multi-model routing, hardware-aware scheduling) signals a maturing managed alternative to self-built vLLM fleet management — worth tracking as it informs the build-vs-buy framing for LLM serving infrastructure.
- Platform/SRE — Plan: This GA relaunch adds cross-account event sharing via RAM, strict ordering, CloudEvents format support, and up to 1-year retention — capabilities worth evaluating this quarter if the platform uses EventBridge for inter-team or multi-account event routing.
- CI/CD — Skip
- Leader — Learn: New enterprise-grade EventBridge capabilities (cross-account brokering, CloudEvents, retention) could reshape how the org designs event-driven platform integrations, but no strategic or cost decision is forced now.
- Platform/SRE — Plan: Self-hosted GitLab operators should schedule patching to 19.4.1, 19.3.3, or 19.2.7 this sprint; GitLab’s ‘Critical’ classification signals high-severity CVEs, but no KEV listing or active exploitation is confirmed in the signals, so Act threshold is not met.
- CI/CD — Plan: If GitLab is the CI/CD platform, queue an upgrade to the appropriate critical patch release (19.4.1/19.3.3/19.2.7) within the current sprint; no confirmed supply-chain compromise or exploitation evidence, but critical-severity vulnerabilities in the CI platform warrant prompt scheduling.
- Leader — Skip
- Platform/SRE — Plan: A semver-major release that removes retired GCP service resources and changes provider defaults — teams running GCP workloads via Terraform should plan a version pin audit and config migration before upgrading, as breaking changes will surface at apply time. No forced deadline exists, but deferring widens the upgrade gap.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found) · GA announcement · major release (8.0)
- Platform/SRE — Plan: Review any SSH keys used for infrastructure automation against GitHub repos (deploy keys, Ansible/Terraform git sources) to confirm they meet the new algorithm and minimum RSA key-size requirements before the removals take effect; no hard deadline is published yet.
- CI/CD — Plan: Audit SSH deploy keys and runner SSH credentials used to pull private repos or push artifacts via GitHub to ensure they use accepted algorithms and sufficiently large RSA keys; schedule rotation for any that don’t comply before the removal lands.
- Leader — Skip
- Platform/SRE — Plan: Teams running EMR on EKS should evaluate migrating production Spark workloads to emr-spark-8.1.0 to take advantage of the new 36-month LTS support window, reducing forced upgrade pressure; no hard deadline exists yet.
- CI/CD — Skip
- Leader — Plan: EMR LTS changes the upgrade economics for data platform teams — evaluate standardizing on LTS releases to extend support cycles and reduce upgrade toil as part of the next data platform planning cycle.
- Platform/SRE — Plan: If your platform runs EMR workloads, this GA release brings notable operational improvements: Serverless shuffle storage raised from 200 GiB to 1 TiB, IPv6 EKS cluster support, and Spark Connect endpoints on EMR on EKS. Schedule evaluation for teams hitting storage or networking constraints this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: CloudWatch Omni is now GA and offers OpenTelemetry interoperability, multi-cloud (including Azure) telemetry, and AI-driven root-cause analysis — worth evaluating this quarter as a replacement or augmentation for existing AWS-based observability pipelines if CloudWatch is already in use.
- CI/CD — Skip
- Leader — Learn: Omni signals AWS’s direction for AI-native, multi-cloud observability and could shift the build-vs-buy calculus for teams invested in third-party observability vendors alongside CloudWatch; no immediate strategic decision required.
- Signals: GA announcement
- Platform/SRE — Plan: Grafana 13.2 (EOL 2027-05-18) ships GA support for named, independent notification policy trees — worth adopting this quarter if you run Grafana-managed alerting across multiple teams. Evaluate upgrading to 13.2 and migrating team-owned alert rules to named policies incrementally.
- CI/CD — Skip
- Leader — Learn: Grafana’s approach to scaling alert routing across team boundaries is useful context when evaluating IDP or observability platform strategy, but no strategic, cost, or vendor-risk decision is required here.
- Signals: Grafana 13.2 EOL 2027-05-18 · GA announcement
- Platform/SRE — Skip
- CI/CD — Learn: A full exportable inventory of SSH keys, PATs, and OAuth tokens touching the enterprise is useful context for supply-chain hygiene thinking, but it introduces no pipeline mechanic to change today.
- Leader — Plan: Schedule a review of GitHub Enterprise credential inventory exports as part of your next access-review or compliance cycle; the capability directly supports audit readiness for SOC 2 / ISO 27001 controls around privileged access.
- 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: If your platform uses Azure Functions with PowerShell workers, plan migration to 7.6 this quarter to stay ahead of older runtime EOL cycles; no forced-upgrade date announced yet.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Teams running ECS workloads can now consolidate deployment health signals — circuit breaker status, alarm state, container and LB health checks — into a single console view instead of jumping between tools. No migration required; worth scheduling time to evaluate and adopt as the standard deployment monitoring workflow.
- CI/CD — Learn: If your ECS-based release process uses canary or blue/green strategies, this console view surfaces traffic-shift progress and task failure diagnostics in one place, but there is nothing to configure or pin — useful context for how to troubleshoot ECS deployment failures faster.
- Leader — Skip
- Platform/SRE — Plan: Grafana is a standard part of the observability stack platform teams own; 13.2.2 patches three CVEs (EPSS ≤ 0.01, none KEV-listed), so no emergency but schedule an upgrade of Grafana instances this sprint to stay current on security fixes.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-15815 — CISA KEV: not listed, EPSS 0.01 · CVE-2026-76154 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-79656 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Three CVEs patched in Grafana — none KEV-listed and all with near-zero EPSS scores, so no active exploitation, but teams running Grafana in their observability stack should schedule an upgrade to 13.1.6 this sprint.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-15815 — CISA KEV: not listed, EPSS 0.01 · CVE-2026-76154 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-79656 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Grafana is a common observability-stack component; 13.0.9 patches three CVEs, none KEV-listed and EPSS scores are negligible (0.01, 0.00, n/a), so no forced-action clock exists — schedule an upgrade to v13.0.9 this sprint as a routine security hardening step.
- CI/CD — Skip
- Leader — Skip
- Signals: major release (13.0) · CVE-2026-15815 — CISA KEV: not listed, EPSS 0.01 · CVE-2026-76154 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-79656 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Grafana is a standard observability component in Platform’s stack; four CVEs are patched in 12.4.11, but none appear in CISA KEV and EPSS scores are near zero, so schedule the upgrade this sprint rather than treating it as an emergency hotfix.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-12704 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-15815 — CISA KEV: not listed, EPSS 0.01 · CVE-2026-76154 — CISA KEV: not listed, EPSS 0.00
- 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 — Plan: containerd 2.4.0 is a GA non-LTS release that removes previously deprecated features, so audit your current deployments for deprecation warnings before upgrading; the 2.3 LTS remains the stability-first choice, and this release’s EOL is 2027-05-16.
- CI/CD — Skip
- Leader — Skip
- Signals: containerd 2.4 EOL 2027-05-16 · deprecation mentioned (no explicit date found) · breaking-change flagged
- Platform/SRE — Plan: If you run Backstage, this release removes deprecated catalog APIs (update targetRef usage, replace CodeOwnersProcessor and AnnotateScmSlugEntityProcessor with community modules, remove catalog.stitchingStrategy.mode) and requires Elasticsearch 8.19+; plan the Elasticsearch upgrade and code migration before adopting v1.55.0.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Learn: Pre-written compliance policies in HCP Terraform could simplify governance guardrails for teams using the managed service; worth evaluating for adoption but no operational urgency.
- CI/CD — Skip
- Leader — Plan: If the org uses HCP Terraform, evaluate whether native pre-written policy sets can replace or augment custom Sentinel/OPA work to reduce compliance overhead — schedule a review this quarter.
- 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 — Skip
- CI/CD — Plan: Adopt the new ‘stage only’ permission when minting npm automation tokens to enforce least-privilege publishing; schedule a rotation of existing CI npm tokens to apply the tighter scope and reduce blast radius from a leaked credential.
- Leader — Skip
- Platform/SRE — Plan: If you run Azure PostgreSQL Flexible Server with logical replication, add the new logical_replication_slot_sync_status Azure Monitor metric to your dashboards and alerts this quarter to catch slot lag before it bloats WAL retention.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Three new GA capabilities directly relevant to EKS workload resilience: scoped resource discovery via existing K8s labels, AI-powered dependency pattern analysis, and cross-account policy sharing via AWS Organizations. Evaluate integrating Resilience Hub into the platform runbook this quarter.
- CI/CD — Skip
- Leader — Learn: Organization-wide resilience policy sharing through AWS Organizations is a governance capability worth tracking as a potential standard for cross-team resilience posture, but no immediate strategic decision is required.
- Platform/SRE — Plan: GA capability that replaces per-resource PrivateLink configurations with shareable CIDR ranges via RAM and GENEVE encapsulation — evaluate whether this simplifies existing multi-account or vendor-access network architectures this quarter.
- CI/CD — Skip
- Leader — Learn: New cross-account connectivity model for vendor access patterns; introduces hourly and per-GB pricing worth factoring into future multi-account networking cost models, but no forced decision today.
- Platform/SRE — Plan: New GA capability worth evaluating this quarter: workloads that currently split or offload large SNS payloads can be simplified by setting the new MaximumMessageSize topic attribute on Standard or FIFO topics, though note the constraint of up to 100 subscriptions per topic at the larger size.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: ECS Express Mode now supports ARM64 as a GA option, enabling Graviton-powered workloads with up to 40% better price-performance. Worth evaluating as an architecture choice for new or cost-sensitive services this quarter, with no deadline pressure.
- CI/CD — Skip
- Leader — Plan: Graviton ARM64 support in ECS Express Mode represents a concrete FinOps opportunity — evaluate adopting Graviton as part of the standard compute profile to capture the claimed 40% price-performance improvement in this quarter’s platform roadmap.
- Platform/SRE — Skip
- CI/CD — Plan: ubuntu-latest will migrate to Ubuntu 26.04, which can silently change pre-installed toolchain versions and break pipelines; audit workflows using ubuntu-latest and validate against ubuntu-26.04 before the cutover date GitHub publishes.
- Leader — Skip
- Signals: Ubuntu 26.04 EOL 2031-05-29 · GA announcement
- 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 — Skip
- CI/CD — Skip
- Leader — Plan: GitLab 19.4 introduces per-team and per-user AI credit budgets with exportable usage reports — if your org allocates AI spend across departments on GitLab, evaluate enabling these controls this quarter to satisfy the AI governance and budget-accountability requirements your finance and compliance stakeholders are increasingly asking for.
- Signals: GitLab 19.4 reaches EOL in 90d (2026-12-17)
- Platform/SRE — Skip
- CI/CD — Plan: Workflow execution protections are now GA for GitHub Enterprise, orgs, and repos; schedule adoption of allowlist controls to restrict who can trigger workflows as a supply-chain hardening step this quarter.
- Leader — Plan: This GA feature enables org-wide policy on who may trigger GitHub Actions workflows; evaluate adding it to your golden-path security standards and internal developer platform requirements.
- Signals: GA announcement
- Platform/SRE — Plan: Cloud SQL (MySQL and PostgreSQL) now auto-enables PITR after DR switchover/failover asynchronously, reducing RTO — review your DR runbooks to reflect the faster recovery path. The GA Z4D machine series (AMD EPYC Turin, up to 3 TB local storage) is worth evaluating this quarter for storage-heavy workloads like databases, search, or vector stores.
- CI/CD — Skip
- Leader — Learn: The Z4D GA instances and Cloud SQL PITR improvements are worth noting for teams standardizing on GCP for storage-heavy or analytics workloads, but neither forces a strategic decision or pricing change now.
- Signals: GA announcement
- Platform/SRE — Plan: Teams using Transfer Family SFTP behind an NLB for compliance or IP-based access controls should evaluate enabling this feature; no deadline, but it unlocks accurate audit logs and identity-provider IP filtering that may be required for security reviews.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: T8i instances offer up to 30% better price performance than T3 with the same CPU credit model, making them a straightforward drop-in upgrade for burstable workloads like small databases, ingress gateways, or low-traffic internal services; evaluate swapping T3 instances this quarter to reduce compute TCO.
- CI/CD — Learn: T8i instances are explicitly called out as suitable for CI/CD pipelines and could reduce runner costs compared to T3, but no pipeline migration is required — worth noting if self-hosted runners are being right-sized.
- Leader — Plan: T8i delivers up to 30% better price performance over T3 with no migration complexity due to compatible CPU credit mechanics; flag this for the next FinOps review as a low-effort TCO reduction for burstable workload fleets.
- Signals: GA announcement
- Platform/SRE — Plan: Kubernetes v1.37 GA ships emptyDir permission modes (including sticky bit) and bind mount options (noexec, nosuid, nodev) — schedule evaluation and adoption as part of your 1.37 upgrade cycle to harden shared writable volumes; no forced deadline until EOL 2027-10-28.
- CI/CD — Skip
- Leader — Skip
- Signals: Kubernetes 1.37 EOL 2027-10-28
- Platform/SRE — Learn: Reduces friction for credential management in GitHub Enterprise Cloud environments, but this is an admin/policy feature with no infrastructure operational urgency.
- CI/CD — Plan: If pipelines use classic PATs or SSH keys in SSO-enforced orgs, automating authorization can eliminate manual unblocking steps — worth scheduling a review of affected credentials and updating provisioning workflows.
- Leader — Learn: Marginally improves developer onboarding and access management in GitHub Enterprise Cloud; no strategic, cost, or vendor-risk implication requiring a decision.
- Platform/SRE — Plan: S3 Files now reaches feature parity across all three ECS launch types; evaluate adopting shared S3-backed volumes for data-intensive EC2 workloads this quarter to eliminate data staging overhead.
- CI/CD — Skip
- Leader — Learn: ECS S3 Files now uniform across EC2, Fargate, and Managed Instances — useful context when evaluating EC2 vs Fargate positioning for data-heavy or AI-agent workloads on the platform.
- Platform/SRE — Skip
- CI/CD — Learn: GHAS enforcement is a GitHub admin feature, not a pipeline change, but CI/CD engineers should understand that enterprise-level security configurations may now be locked — worth noting if code-scanning settings are managed in repo workflows.
- Leader — Plan: This new enforcement capability lets enterprise admins lock GHAS settings so org/repo owners can’t override them — evaluate adopting enterprise-wide enforcement to standardize code-scanning and security policies across all organizations this quarter.
- Platform/SRE — Plan: Cilium 1.20 is a GA minor release of a CNI/service-mesh stack platform teams operate directly; new ENI IPAM for IPv6 and Gateway API ExternalAuth are worth evaluating for adoption this quarter, and the TCPRoute/UDPRoute additions may change how non-HTTP traffic routing is architected on the cluster.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Two Go library security fixes (compress, x/crypto) plus serious TSDB bugs — deleted series causing missing samples after restart and out-of-order queries blocking compaction for hours causing memory growth — make this a priority upgrade for any team on Prometheus 3.13.x; no KEV listing or hard deadline, but schedule 3.13.3 upgrade this sprint.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: Notable operational improvements: concurrent status computation eliminates multi-minute delays and the resync period drops from 1 hour to 3 minutes. Plan an upgrade this quarter; no hard deadline but the perf gains are production-relevant for clusters running many releases.
- CI/CD — Plan: SOURCE_DATE_EPOCH support for reproducible chart archives and expanded GnuPG keybox provenance support are concrete supply-chain hardening gains; also fixes a template regression routing messages to stderr. Schedule adoption this quarter to improve build reproducibility and provenance workflows.
- Leader — Skip
- Platform/SRE — Plan: Minor feature release of Helm with k8s API group updated to 0.37.0; schedule an upgrade this quarter to stay current, but no EOL date or forced migration deadline exists.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run Google Cluster Toolkit for HPC workloads, review the linked security bulletin and apply Slurm patches; no KEV or active exploitation signal, but a vulnerable job scheduler carries real risk. All other items (AlloyDB audit monitoring, MCP) are minor or pre-GA.
- CI/CD — Skip
- Leader — Learn: The Public Preview of MCP support in API Gateway is an early signal for orgs evaluating AI-agent integration patterns — it shows GCP moving to expose REST APIs as agent tools without backend changes, worth tracking as the feature matures toward GA.
- Platform/SRE — Plan: If you run LLM inference workloads on SageMaker HyperPod, this GA feature cuts scale-out time ~60% by pre-loading model weights to NVMe and pre-pulling container images; evaluate adding a modelCacheConfig block to InferenceEndpointConfig resources this quarter.
- CI/CD — Skip
- Leader — Learn: HyperPod’s new model caching substantially narrows the cold-start penalty for large-model inference, which is relevant context if evaluating HyperPod as the org’s managed inference platform versus self-managed alternatives.
- Platform/SRE — Plan: If your team uses Grafana Cloud Synthetic Monitoring with custom labels, plan to migrate dashboards, SLOs, alerts, and PromQL queries to the new label format (no
label_prefix, labels on all check metrics) before the March 1, 2027 deadline to avoid breakage. - CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Organizations self-hosting GitLab on their clusters should schedule an upgrade to 19.3.2, 19.2.6, or 19.1.8; the ‘Critical’ designation signals high-severity CVEs, but no KEV or active exploitation is confirmed in the signals, so this is a prompt-but-planned patch rather than an emergency.
- CI/CD — Plan: GitLab is a core CI/CD platform; a critical-labeled patch release warrants updating self-hosted instances promptly — plan the upgrade to the relevant supported minor (19.3.2 / 19.2.6 / 19.1.8) this sprint, but no confirmed exploitation anchor elevates this to Act.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: New GA GitHub Actions feature lets you scope cache read/write permissions per workflow or job, reducing blast radius of a compromised workflow. Evaluate and adopt cache-mode across pipelines this quarter as a supply-chain hardening step.
- Leader — Skip
- Platform/SRE — Plan: Teams using Transit Gateway inter-Region peering can now add network health indicators to CloudWatch dashboards and alarms, reducing time to isolate AWS-side degradation; evaluate adding NHI alarms to existing TGW peering path monitoring this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run S3 File Gateway for regulated workloads, you can now route FIPS-compliant traffic over PrivateLink instead of the public internet — plan to create FIPS VPC endpoints and upgrade gateway software to 2.1.10 or later to enable this.
- CI/CD — Skip
- Leader — Learn: This expands compliance options for regulated workloads using AWS Storage Gateway, potentially simplifying FIPS requirements in GovCloud or heavily regulated environments — no immediate decision required.
- Platform/SRE — Plan: New GA hardware option delivers up to 2,688 vCPU in a 42U rack for space-constrained on-prem deployments; platform teams evaluating hybrid or edge architectures should assess whether it fits their latency or data-residency requirements this quarter.
- CI/CD — Skip
- Leader — Learn: Second-gen single-rack Outposts expands the on-prem compute tier for orgs with edge or data-residency constraints; worth tracking as context for hybrid-cloud build-vs-buy decisions but no immediate strategic action required.
- Signals: GA announcement
- Platform/SRE — Plan: If your org runs ECS and uses IAM SCPs or permission boundaries to govern resource allocation, update your IAM policies to enforce ecs:task-cpu and ecs:task-memory on RunTask and StartTask — this closes a gap where those controls were previously bypassable at launch time.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: This GA feature meaningfully improves API Gateway observability: 1 KB log truncation was a real debugging blind spot, and the new ability to route up to 1 MB events to S3 (Parquet/Athena), CloudWatch, or Firehose simultaneously is worth adding to the observability platform this quarter. Plan to reconfigure API Gateway REST API logging destinations and validate cost impact under vended logs pricing.
- CI/CD — Skip
- Leader — Learn: The shift to vended logs pricing and multi-destination routing is relevant for observability cost architecture — routing long-term logs to S3/Athena instead of CloudWatch can reduce ingestion costs — but no strategic decision or vendor risk is triggered here.
- Platform/SRE — Skip
- CI/CD — Plan: New GA GitHub capability lets teams enforce secret-blocking via repository rulesets; schedule a rollout to enable this across all repos as a supply-chain hardening step this quarter.
- Leader — Plan: This is a concrete org-wide policy lever — evaluate mandating the new secret-blocking ruleset as a standard across all GitHub repositories to reduce credential-leak risk at the merge gate.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: If your org has standardized on GitHub Copilot Business or Enterprise, evaluate this new central permission model to define which agent operations require human approval vs. run autonomously — a governance decision worth setting org policy on this quarter.
- 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 your pipelines run CodeQL on ARM64 Linux runners, upgrading to 2.27.0 unlocks native support; also worth evaluating the new Rust security query and expanded Java/Kotlin and C# framework coverage for any affected repositories.
- Leader — Skip
- Platform/SRE — Plan: GA availability of full-caching ephemeral OS disks can meaningfully reduce node boot times and eliminate remote-storage I/O for node pools — worth evaluating for VMSS-backed AKS node groups this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: GovCloud operators running EKS with cert-manager and service meshes like Istio or Linkerd should evaluate adopting the Private CA EKS add-on to automate TLS certificate lifecycle; no deadline, but it simplifies a previously manual integration.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: This GA capability removes a key architectural constraint that pushed long-running workloads off Lambda toward ECS/Batch/Step Functions; evaluate whether existing workarounds in the platform’s serverless stack can be simplified this quarter.
- CI/CD — Skip
- Leader — Learn: The 6x timeout increase changes the serverless vs. dedicated-compute trade-off for batch and AI inference workloads, worth factoring into the next platform strategy review, but no urgent decision is required.
- Platform/SRE — Plan: If your org uses Lambda Managed Instances, evaluate migrating capacity providers to Graviton5 instance types (C9g, M9g) for up to 25% compute performance improvement at EC2 pricing; no deadline, but worth scheduling this quarter.
- CI/CD — Skip
- Leader — Learn: Graviton5 support in Lambda Managed Instances offers a potential cost/performance lever for teams running Lambda at scale on EC2; worth tracking as a FinOps input but no strategic decision required now.
- Platform/SRE — Plan: GHES 3.22 GA means teams running self-hosted GHES should plan an upgrade evaluation this quarter. No forced-upgrade deadline is present, but a new minor release with platform-wide changes warrants scheduling a controlled upgrade project.
- CI/CD — Learn: If your pipelines run on GitHub Actions hosted on GHES, this version bump may eventually surface new runner or Actions capabilities, but the release summary is too thin on CI/CD specifics to warrant a pipeline change today.
- Leader — Learn: GHES 3.22 adds capabilities including Copilot CLI for administrators — worth tracking as context for AI-tooling standardization, but no licensing, pricing, or strategic forcing function is present in this release.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: Dependabot can now pull from private GitHub Packages registries without a PAT, using the existing ‘Manage Actions access’ permission — evaluate removing hardcoded tokens from Dependabot config to simplify credential management and reduce secret sprawl.
- Leader — Skip
- Platform/SRE — Plan: New GA S3 Object Lock capability lets you anchor WORM retention to a future event (contract close, audit complete) rather than a fixed date — relevant for platform teams managing compliant storage under SEC 17a-4(f), FINRA 4511, or CFTC 1.31. Evaluate updating your S3 bucket policies and IAM condition keys to adopt event holds for regulated data this quarter.
- CI/CD — Skip
- Leader — Learn: If the org operates in regulated industries, this Cohasset-assessed S3 capability closes a gap in event-driven retention compliance at no additional cost — useful context for understanding your AWS compliance posture, but no strategic decision or budget action required.
- Platform/SRE — Plan: GA feature enabling ACM-backed mTLS from API Gateway to backend services — worth adopting for any zero-trust or regulated workload this quarter; audit existing REST API integrations and plan certificate provisioning via ACM or AWS Private CA.
- CI/CD — Skip
- Leader — Learn: Closes a common compliance gap in regulated industries (finance, healthcare) by extending mTLS to the API-to-backend path; relevant context if the org is pursuing zero-trust architecture or FedRAMP/HIPAA posture.
- Platform/SRE — Plan: CNCF graduation signals Karmada is production-vetted; platform teams running multiple clusters or hybrid AI infrastructure should evaluate it as a multi-cluster orchestration candidate this planning cycle.
- CI/CD — Skip
- Leader — Learn: Karmada’s graduation shifts the multi-cluster management landscape—worth tracking as context for build-vs-buy decisions on cross-cluster federation, but no forced decision yet.
- Platform/SRE — Plan: If your org uses GCP Compute Engine reservations across projects, you can now convert between single-project and shared reservations without recreating them — worth evaluating for multi-team capacity-sharing workflows this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: If you run memory-intensive workloads (databases, in-memory caches) in any of these four newly covered regions, evaluate migrating from M8g to M9g this quarter for up to 25% better compute performance and the new Nitro Isolation Engine security guarantees.
- CI/CD — Skip
- Leader — Learn: Graviton5-based M9g instances reaching more regions broadens the Arm-based compute option for cost and performance optimization; useful context for the next FinOps or instance-family review, but no strategic decision is forced.
- Platform/SRE — Plan: New GA ECS capability worth evaluating this quarter, especially for GPU or other constrained-capacity workloads where task launch latency inflates deployment windows; review healthy-percent thresholds and source-revision cleanup mode (BLOCKING vs DEFERRED) for your services.
- CI/CD — Plan: ECS deployments can now signal success before full scale-out, directly unblocking downstream pipeline stages; plan to configure Early Success Criteria on services where slow task launches currently stall pipeline gates.
- Leader — Skip
- Platform/SRE — Plan: DRA Extended Resource support is now stable in 1.37, letting existing extended-resource workloads (e.g. example.com/gpu) route through DRA drivers without ResourceClaims or device plugins — a meaningful adoption path to evaluate this quarter. EOL for 1.37 is 2027-10-28, so no forced upgrade yet; plan an evaluation of DRA adoption for GPU/device workloads in the current planning cycle.
- CI/CD — Skip
- Leader — Learn: DRA reaching GA means GPU and accelerator workloads can now use a unified allocation model without dual plugin stacks — worth understanding for future platform architecture decisions around AI/ML infrastructure, but no toolchain strategy or budget action is required now.
- Signals: Kubernetes 1.37 EOL 2027-10-28
- Platform/SRE — Skip
- CI/CD — Plan: Multiple trusted publishing configurations per npm package are now GA on GitHub, enabling more flexible provenance-backed release workflows; schedule a review of existing npm publish pipelines to adopt multi-config trusted publishing and reduce reliance on long-lived tokens.
- Leader — Skip
- Signals: GA announcement
- 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 — Plan: The new REST API surfacing runner version deprecations lets you proactively query upcoming retirements before they silently red-line pipelines. Integrate it into pipeline monitoring this quarter; no hard date was found in the signals, so this is a scheduled improvement rather than an emergency.
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Learn: If your team uses CloudFront flat-rate plans, you can now automate subscription management via CloudFormation/CDK instead of manual console steps — useful for IaC-driven workflows but no operational change required today.
- CI/CD — Skip
- Leader — Plan: If the org is evaluating CloudFront flat-rate plans for cost predictability, API-driven subscription management now makes it viable to automate within IaC pipelines — worth assessing during the next cloud cost review cycle.
- Platform/SRE — Plan: New GA capability lets platform teams route FIPS-validated S3 traffic entirely within the VPC — actionable for teams running regulated or federal workloads; schedule a review of existing VPC endpoint configs and update to the FIPS S3 endpoint where compliance requires it.
- CI/CD — Skip
- Leader — Learn: Useful signal for leaders with federal or regulated customers — AWS now offers a path to keep S3 traffic VPC-internal under FIPS 140-3, which may simplify future compliance audits or contract negotiations with government clients.
- Platform/SRE — Plan: Teams running MWAA Provisioned environments should evaluate the new one-click recommended alarms and built-in metrics dashboard as a quick win for observability coverage without manual CloudWatch alarm configuration.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Teams running ECS with Managed Daemons for logging or metrics collection should evaluate configuring auxiliary daemons as non-critical to prevent churn on mission-critical tasks; no deadline, but worth adopting this quarter when reviewing ECS daemon configurations.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: Audit build scripts, custom GitHub Actions, and any Node.js-based pipeline tooling for vm2 usage; if found, update to 3.11.7 and disable require.external — the blog post describes a working exploit path (CVSS 10.0), so exposure is concrete even without a KEV entry. No forced deadline, but the publicly documented exploit makes this a near-term project, not a watch item.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: If your pipelines use CodeQL scanning, upgrading to 2.26.4 improves detection coverage for GitHub Actions security issues and adds Go 1.27 support — schedule the version bump this quarter.
- Leader — Skip
- Platform/SRE — Plan: GA capability that reduces container image cold starts to sub-second by snapshotting initialized environments; worth adopting this quarter for latency-sensitive Lambda workloads (ML inference, interactive APIs) running on container images.
- CI/CD — Skip
- Leader — Learn: SnapStart extending to container images changes the cost/performance tradeoff for serverless-based architectures, informing build-vs-buy and platform strategy discussions around cold-start optimization.
- Platform/SRE — Plan: New GA Config coverage for resources platform teams commonly operate — EKS::PodIdentityAssociation, RDS::DBProxy, EC2 route servers, and Organizations::Policy — is worth enabling in your Config recording and aggregator configuration this quarter to close compliance gaps. No deadline, but teams already using Config for compliance should audit which of the 60 new types overlap with their environment.
- CI/CD — Skip
- Leader — Skip
- 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 — 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 — Plan: If your org runs Vault Enterprise and is deploying AI agent workloads, this GA feature adds purpose-built IAM controls worth evaluating this quarter; no forced migration or deadline, but assess whether your current Vault version and license tier expose it.
- CI/CD — Skip
- Leader — Learn: This signals Vault Enterprise is extending its security model to cover AI agent identities; worth noting if AI agent adoption is on the roadmap and the org is already standardized on Vault Enterprise, but no strategy or contract decision is required now.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: If the org runs GHES and is evaluating a move to GitHub Enterprise Cloud with Data Residency, this GA milestone removes the primary operational risk (downtime) from the migration path — worth scheduling an evaluation this quarter.
- Signals: GA announcement
- Platform/SRE — Plan: If your platform runs Azure Container Apps, this GA feature lets you consolidate posture management under Defender for Cloud rather than operating a separate security toolchain; evaluate enabling it this quarter.
- CI/CD — Skip
- Leader — Learn: Extends unified container security posture to serverless workloads on Azure — worth noting if your org is standardizing on Defender for Cloud as the security management plane.
- Signals: GA announcement
- Platform/SRE — Plan: CVM node pools on AKS are now GA, enabling sensitive workload isolation at the hardware level; evaluate whether regulated or high-sensitivity workloads in your clusters warrant migrating to CVM node pools this quarter.
- CI/CD — Skip
- Leader — Learn: GA confidential compute on AKS is a new capability relevant to compliance and data-sovereignty positioning, but no immediate strategic decision is required unless the org has active regulated-workload requirements on Azure.
- Signals: GA announcement
- Platform/SRE — Plan: New GA capability unifies monitoring of self-managed PostgreSQL on EC2 alongside RDS/Aurora in a single console; worth evaluating if you run mixed database fleets to consolidate your observability stack.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: This GA capability lets platform teams migrate high-volume compliance and audit Azure tables to the lower-cost Auxiliary plan without rebuilding pipelines. Evaluate which existing Log Analytics tables qualify for plan switching this quarter to reduce observability ingestion costs.
- CI/CD — Skip
- Leader — Plan: The plan-switching capability is a concrete FinOps lever for reducing Azure Monitor spend on high-volume, rarely-queried compliance logs. Worth scheduling an audit of Log Analytics table plans to identify cost-reduction opportunities within the current planning cycle.
- Signals: GA announcement
- Platform/SRE — Plan: If you operate workloads in Azure Government or Azure China, this new GA log tier offers a cheaper ingestion and retention path for high-volume compliance/audit logs — evaluate whether shifting verbose log streams to Auxiliary tables reduces your Monitor costs this quarter.
- CI/CD — Skip
- Leader — Learn: Auxiliary Logs adds a cost-effective tier for compliance and audit log retention in sovereign cloud regions; useful context if the org has Azure Government or China footprint and is managing observability spend, but no strategic decision is forced.
- Signals: 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: StorageVersionMigration API (storagemigration.k8s.io/v1) is now stable and enabled by default in Kubernetes 1.37, removing the need for manual migration scripts when promoting or dropping CRD API versions. Plan to incorporate SVM into your CRD lifecycle runbooks when scheduling the upgrade to 1.37 (EOL 2027-10-28).
- CI/CD — Skip
- Leader — Skip
- Signals: Kubernetes 1.37 EOL 2027-10-28 · GA announcement
- Platform/SRE — Plan: Teams using ASR on AWS should evaluate the AI Toolkit and expanded GuardDuty/Inspector/Macie coverage; the enhanced console replaces manual DynamoDB/SSM config, making this a worthwhile platform security upgrade to schedule this quarter.
- CI/CD — Skip
- Leader — Learn: The shift from manual SSM Automation expertise to AI-guided remediation generation signals a meaningful reduction in barrier-to-entry for automated security response — worth tracking as an indicator of where cloud-native security tooling is heading.
- Platform/SRE — Plan: New GA AWS service adds cross-account agent catalog support via CloudFormation, Terraform, CDK, and AWS RAM — worth evaluating this quarter if your org is building shared AI agent infrastructure, as it may change how you architect agent discovery and access control across accounts.
- CI/CD — Skip
- Leader — Learn: AWS Agent Registry offers a governed, org-wide catalog for AI agents and tools with audit trails and cross-account sharing; worth tracking as a pattern for AI governance strategy, but no immediate decision or vendor-risk event is present.
- Signals: GA announcement
- Platform/SRE — Plan: If Redshift is in your stack and you have data residency or network-isolation requirements, this is worth adopting: SSO via IAM Identity Center with all auth traffic staying inside your VPC via PrivateLink. Evaluate enabling EVR and wiring up Identity Center for your provisioned clusters or serverless workgroups this quarter.
- CI/CD — Skip
- Leader — Learn: Redshift now supports SSO via IAM Identity Center with network traffic fully contained in your VPC — relevant context if your org has regulatory or data-residency mandates for analytics infrastructure, but no decision is forced by this launch.
- Platform/SRE — Plan: New GA Graviton5 memory-optimized instances offer up to 25% better compute and 30% faster database performance vs R8g; evaluate migrating memory-intensive workloads (Kubernetes nodes, caches, databases) this quarter to capture the price-performance gains.
- CI/CD — Skip
- Leader — Learn: Graviton5 R9g instances establish a new price-performance ceiling for memory-intensive workloads on AWS; useful context for future FinOps and instance-family standardization decisions but no forcing function today.
- Signals: GA announcement
- Platform/SRE — Plan: New GA WarmUpConfiguration parameter lets teams delay alarm evaluation after resource creation, reducing on-call noise from missing-data transitions during startup. Update IaC alarm definitions (Terraform/CloudFormation) to include warm-up periods for resources that take time to begin emitting metrics.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA minor release of a core IaC tool with meaningful platform capabilities: import blocks inside modules, a store block for ephemeral/sensitive values across plan and apply, and on_failure modes for resource action triggers. No breaking changes or EOL deadline, but worth scheduling evaluation and adoption this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you use Pulumi with connection-string URLs (e.g. Postgres), upgrade to sdk/v3.260.0 to prevent passwords leaking into state/log output; no hard deadline but a meaningful security hygiene improvement.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Kubernetes 1.37.0 is a new minor release worth evaluating for adoption this quarter; review the CHANGELOG for API removals or deprecations that may affect running workloads before scheduling an upgrade window.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: A new Istio minor release is always a candidate for upgrade planning — review the full release notes for breaking changes, API removals, or deprecations before scheduling a mesh upgrade this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: v1.39.1 fixes multiple CVEs in Envoy’s HTTP/3 (UAF, CVE-2026-73512), HTTP/2 (process termination, CVE-2026-73513), and connection-handling paths — real data-plane exposure for any Istio, Contour, or Envoy-based ingress deployment. None are KEV-listed or confirmed exploited, so schedule patching this sprint rather than treating it as an emergency.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-73511 — CISA KEV: not listed, EPSS n/a · CVE-2026-73512 — CISA KEV: not listed, EPSS n/a · CVE-2026-73513 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Envoy is a common data-plane component in service meshes and ingress layers; this patch addresses a use-after-free in HTTP/3, process-termination bugs in HTTP/2, and multiple URL-normalization bypasses. No KEV listing or known active exploitation, so no hard deadline, but upgrade to v1.38.4 should be scheduled this sprint for any fleet running Envoy.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-73511 — CISA KEV: not listed, EPSS n/a · CVE-2026-73512 — CISA KEV: not listed, EPSS n/a · CVE-2026-73513 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Nine CVEs addressed including a UAF on HTTP/3, abnormal process termination on HTTP/2 trailers and ext_authz CONNECT requests, and a shared upstream connection-poisoning bug via HTTP upgrade — none are KEV-listed but the severity warrants scheduling an upgrade to v1.37.6 this sprint for any cluster running Envoy as ingress or data-plane proxy.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-73511 — CISA KEV: not listed, EPSS n/a · CVE-2026-73512 — CISA KEV: not listed, EPSS n/a · CVE-2026-73513 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Backstage is IDP infrastructure platform engineers commonly operate; this patch carries security fixes with no CVE details or KEV/exploitation data in the signals. Schedule upgrade to 1.49.6 within the current patch cycle — no hard deadline anchors Act.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you self-host Backstage as your internal developer platform, schedule an upgrade to 1.50.5; the release is flagged as a security fix recommended for all 1.50 users, though no specific CVE or active-exploitation evidence is provided in the signals to anchor an Act verdict.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Teams running Argo CD should schedule an upgrade to 3.4.8 this sprint: it patches three CVEs in UI JS dependencies (none KEV-listed, EPSS ≤ 0.01) and fixes an auto-sync regression that silently skips syncs when a newer commit arrives during an active sync. No hard deadline, but the sync bug is a silent correctness risk on busy clusters.
- CI/CD — Skip
- Leader — Skip
- Signals: Argo CD 3.4 supported · CVE-2026-14257 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-49978 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-59869 — CISA KEV: not listed, EPSS 0.01
- Platform/SRE — Plan: Pod Certificates and Cluster Trust Bundles reaching GA in Kubernetes 1.37 introduces native X.509/mTLS workload identity as an alternative to service account JWTs; evaluate adopting cluster trust bundles and pod certificate issuance this quarter for services requiring mTLS.
- CI/CD — Skip
- Leader — Learn: Native X.509 workload identity baked into Kubernetes core shifts how orgs can approach service-to-service auth without a service mesh; worth tracking as input to future golden-path and identity-standards decisions.
- Signals: Kubernetes 1.37 EOL 2027-10-28
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: GitHub Copilot billing and policy changes affect org-wide licensing costs and seat management; review the three upcoming changes and assess contract or budget impact before they take effect.
- Platform/SRE — Skip
- CI/CD — Plan: Starting October 1, 2026, GitHub Actions retention settings will also govern checks, workflow runs, and commit statuses — review your current retention configuration to ensure historical build data and compliance audit trails are preserved as expected before the change takes effect.
- Leader — Skip
- Platform/SRE — Plan: Teams running Amazon Linux 2023 or other systemd-only distros no longer need disk-export workarounds to ship structured journal logs to CloudWatch. Update the CloudWatch agent to the latest version and add a journald config block to consolidate logging for those instances this quarter.
- CI/CD — Skip
- Leader — Skip
- 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: If you run HCP Vault Dedicated on Azure and use Microsoft Sentinel for SIEM, schedule building the Terraform-managed audit log pipeline described here; no deadline exists, but closing this observability gap is a concrete infrastructure task worth adding to the backlog this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run Mountpoint in EKS or other memory-constrained environments, upgrading to the latest release lets you set explicit memory targets or rely on automatic container-limit detection, preventing the expansion-over-time instability that previously competed with ML or analytics workloads. No deadline, but worth scheduling as a planned upgrade this quarter if Mountpoint is in your stack.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: A new GA Kubernetes minor release with 16 enhancements graduating to Stable and one deprecation/removal is a direct platform concern; audit the removal for any API or feature you currently use and schedule cluster upgrade evaluation this quarter — no forced-upgrade date was found, so Act isn’t warranted yet.
- CI/CD — Skip
- Leader — Learn: Kubernetes v1.37 reflects continued platform maturity but carries no licensing, cost, or vendor-risk angle and no forced-migration deadline; awareness is useful for roadmap conversations, but no leadership decision is pending.
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: If your org uses HCP (Vault, Terraform Cloud, etc.) and an external IdP, evaluate enabling SCIM provisioning to automate user/group sync and reduce manual access management overhead; no deadline, but worth scheduling this quarter.
- CI/CD — Skip
- Leader — Plan: SCIM provisioning on HCP reduces IAM admin overhead and improves access consistency across HCP services — worth adding to your identity governance standards review if the org is standardized on HashiCorp HCP.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: Organizations on Copilot Business or Enterprise should review and configure their global model policy now, as enforcement is actively rolling out and unreviewed defaults may not match org AI governance requirements.
- 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 — Skip
- CI/CD — Plan: The GA rule insights dashboard gives pipeline and release teams visibility into how GitHub enforces branch protection and ruleset policies; worth enabling at the org level to surface enforcement gaps in your release process.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Cloud SQL Proxy V1 (‘cloud_sql_proxy’) is removed from gcloud SDK 582.0.0 — audit infrastructure automation and connection scripts for V1 references and migrate to ‘cloud-sql-proxy’ V2 before upgrading gcloud to 582.0.0.
- CI/CD — Plan: If pipelines use gcloud to establish Cloud SQL connections or reference the removed api-registry MCP commands, they will break on upgrade to gcloud 582.0.0 — audit pipeline scripts and update to Cloud SQL Auth Proxy V2 before rolling out the new SDK version.
- Leader — Skip
- Signals: breaking-change flagged
Plan
archived
EC2 Capacity Reservation Resource Groups now support Capacity Blocks and interruptible reservations
- Platform/SRE — Plan: If your platform manages ML workloads or uses mixed reservation types, this GA change lets you consolidate Capacity Blocks and interruptible ODCRs into unified resource groups with prioritization and On-Demand fallback — worth incorporating into capacity planning and Auto Scaling group configs this quarter.
- CI/CD — Skip
- Leader — Skip
Plan
archived
AWS Secrets Manager adds native rotation for Cisco Security Platform and Netskope tokens
- Platform/SRE — Plan: If your platform integrates Cisco Security Cloud Control or Netskope, you can now remove any custom Lambda rotation logic and let Secrets Manager handle scheduled credential rotation natively; worth scheduling a migration this quarter for affected integrations.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA capability that changes the connectivity architecture for Lambda MicroVMs in regulated environments — if you operate Lambda MicroVMs today or are evaluating them for compliance-sensitive workloads, schedule an evaluation to replace public-internet API paths with PrivateLink VPC Endpoints.
- CI/CD — Skip
- Leader — Learn: For organizations in financial services, healthcare, or government, this GA capability reduces a compliance blocker for Lambda MicroVM adoption, but no licensing, pricing, or vendor-risk decision is triggered — file as context for regulated-workload platform strategy.
- Platform/SRE — Plan: If your platform runs GPU or compute-intensive batch jobs on self-managed EC2 via AWS Batch, this GA feature shifts AMI patching and instance lifecycle management to AWS — worth evaluating for reduction in operational overhead this quarter.
- CI/CD — Skip
- Leader — Learn: AWS Batch on ECS Managed Instances could change the build-vs-manage calculus for GPU batch workloads, offloading patching overhead to AWS — worth noting as a potential cost and ops trade-off in future platform reviews.
- Platform/SRE — Plan: This GA release moves AKS packet forwarding into the kernel via eBPF, potentially reducing latency and CPU overhead for networking-heavy workloads; plan evaluation and enablement on AKS clusters running Advanced Container Networking Services this quarter.
- CI/CD — Skip
- Leader — Learn: AKS is expanding its networking performance story with eBPF-based host routing reaching GA — worth noting as a differentiator when evaluating managed Kubernetes options, but no immediate strategic decision required.
- Signals: GA announcement
- Platform/SRE — Plan: Platform teams managing Lambda in multi-account architectures can now consolidate per-principal permission statements into single policy documents with full IAM condition key support (source IP, principal tags, etc.). Plan a policy consolidation pass for existing Lambda functions to reduce policy sprawl and simplify ongoing management.
- CI/CD — Skip
- Leader — Learn: This GA capability reduces IAM policy complexity for Lambda-heavy multi-account orgs, but it’s an incremental improvement rather than a strategic or cost-model shift — no leadership decision required.
- Platform/SRE — Plan: This GA feature removes the need for an identity broker when authenticating multiple user populations (employees, contractors, CI/CD systems) to EKS clusters. Evaluate whether your clusters could simplify their auth architecture by replacing any intermediary OIDC broker with direct per-provider associations.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: A new GA ECS capability worth adopting this quarter: Fargate and Managed Instances now auto-drain and replace impaired instances, while EC2-based ECS surfaces the new AGENT_CONNECTIVITY health event that teams must wire into their own instance-replacement automation. No deadline, but teams running ECS on EC2 should build the event-driven replacement workflow to gain equivalent resilience.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: CVE-2026-14978 (Unicode normalization in go-slug) can cause files to leak into HCP Terraform/TFE runs despite .terraformignore rules; not KEV-listed and EPSS 0.00, but worth upgrading Terraform to 1.15.9 in the next maintenance window if you upload sensitive files via remote runs.
- CI/CD — Plan: If pipelines run Terraform remote operations against HCP Terraform or Terraform Enterprise, the .terraformignore bypass in CVE-2026-14978 could leak secrets or config files into run uploads; pin Terraform to 1.15.9 in CI pipeline tooling during the next scheduled update.
- Leader — Skip
- Signals: CVE-2026-14978 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Three behavioral changes affect running Prometheus deployments: the stats query-parameter deprecation (other values still work but will be rejected in the next major), the __meta_hetzner_datacenter label drop for hcloud targets, and PromQL duration expressions now enabled by default. Review your relabeling configs, any Hetzner service-discovery rules, and PromQL queries before upgrading; no hard deadline yet since rejection is deferred to the next major release.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation/EOL deadline mentioned: 2026-08-17
- Platform/SRE — Plan: Two security fixes affect IaC workflows: credentials intended for an OCI registry origin can leak to HTTP redirect targets, and tofu init can be forced into high CPU/memory usage via crafted URLs from an attacker-controlled state backend or registry. Upgrade OpenTofu to 1.12.6 in your IaC toolchain this sprint; no KEV listing or confirmed active exploitation, but both issues are directly triggerable in adversarial environments.
- CI/CD — Plan: If tofu init runs in your pipelines against external module/provider registries or remote state backends, both the credential-leak and resource-exhaustion issues apply there too. Pin the OpenTofu version in your pipeline tooling to 1.12.6 as part of your next dependency update cycle.
- Leader — Skip
- Platform/SRE — Plan: CVE-2026-17183 is patched in 13.2.0; EPSS is 0.00 and it is not KEV-listed, so there is no emergency, but schedule an upgrade of self-hosted Grafana this quarter to pick up the security fix and the alerting notifications API migration to v1beta1.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-17183 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Grafana is a common observability stack component; CVE-2026-17183 is not KEV-listed and carries EPSS 0.00, so no active exploitation signal, but schedule an upgrade to 13.1.4 this sprint as standard patch hygiene.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-17183 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: CVE-2026-17183 is fixed in this patch for Grafana, which is common observability infrastructure. Not KEV-listed and EPSS is 0.00, so no forced urgency, but schedule an upgrade to 13.0.7 this sprint as standard security hygiene.
- CI/CD — Skip
- Leader — Skip
- Signals: major release (13.0) · CVE-2026-17183 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Grafana 12.4.9 includes a security fix for CVE-2026-17183 (not KEV-listed, EPSS 0.00 — no active exploitation). Schedule an upgrade to 12.4.9 in your next maintenance window; no emergency action required.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-17183 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: If you operate Backstage, three breaking changes require pre-upgrade review: OAuth redirect URI wildcard semantics changed (audit any custom allowlist patterns before upgrading), the deprecated
config.schemaextension option is removed (update any custom plugins using it), and the early Connections API contract shifted. Schedule the audit and upgrade this quarter. - CI/CD — Skip
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: The M4N machine series is now GA on GCP, offering up to 400 Gbps network and 1M IOPS for memory/network-intensive workloads like vector databases and RAG layers — evaluate whether it fits high-memory workload placements this quarter. CVE-2026-12710 in Application Integration was already patched server-side on April 4, 2026; no customer action required.
- CI/CD — Skip
- Leader — Learn: GCP’s M4N instance family (GA) targets high-memory AI infrastructure workloads such as vector databases and in-memory RAG layers — relevant context for future GCP AI/ML platform architecture discussions, but no immediate strategic or budget decision is forced.
- Signals: GA announcement · CVE-2026-12710 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: The managed EKS Argo CD capability now accepts argocd-cm ConfigMap settings, including custom health checks for CRDs that can hold sync waves until resources finish provisioning. If your clusters use this managed capability, evaluate adding custom health checks for your Custom Resources this quarter.
- CI/CD — Learn: Custom health check logic for CRDs in EKS-managed Argo CD means sync wave advancement can now be gated on actual resource readiness rather than Argo CD’s default no-op behavior; worth factoring into GitOps deployment design if your org uses this specific managed capability.
- Leader — Skip
- Platform/SRE — Plan: If your org runs GitLab Dedicated, the AI Gateway for Duo Agent Platform is now deployable inside your single-tenant environment, keeping AI-processed data in your chosen AWS region. Evaluate this quarter whether to enable it as part of your agentic DevOps rollout.
- CI/CD — Skip
- Leader — Learn: Organizations using GitLab Dedicated for compliance or data-residency reasons can now extend that boundary to AI agent workloads — shapes thinking on how to pursue agentic DevOps without relaxing data-sovereignty requirements.
- Platform/SRE — Plan: Teams self-hosting GitLab should plan an upgrade to 19.3 and note that it reaches EOL on 2026-11-19, meaning another upgrade cycle must be scheduled within the quarter to stay on a supported version.
- CI/CD — Plan: Review the 19.3 release notes for any pipeline syntax, runner, or artifact-handling changes; schedule adoption before the 2026-11-19 EOL to avoid running unsupported GitLab CI infrastructure.
- Leader — Skip
- Signals: GitLab 19.3 reaches EOL in 90d (2026-11-19)
- Platform/SRE — Skip
- CI/CD — Plan: New GA capability in GitLab 19.3 that lets domain experts author Custom Flows via natural language instead of learning the Flow Registry YAML schema; worth evaluating this quarter to reduce the bottleneck between process knowledge and automation authorship.
- Leader — Skip
- Signals: GitLab 19.3 reaches EOL in 90d (2026-11-19)
- Platform/SRE — Plan: Teams self-hosting GitLab should note that 19.3 reaches EOL 2026-11-19 (~90 days); plan an upgrade to 19.4 or later before that date to stay on a supported version.
- CI/CD — Learn: GitLab 19.3 GA adds bulk false-positive dismissal and agentic SAST remediation for existing vulnerability backlogs — worth evaluating if your pipelines already produce GitLab SAST findings, but no urgent action is required.
- Leader — Skip
- Signals: GitLab 19.3 reaches EOL in 90d (2026-11-19)
- Platform/SRE — Skip
- CI/CD — Plan: The Windows 11 arm64 VS2026 runner image is now GA on GitHub-hosted runners; teams building Windows arm64 artifacts should evaluate updating workflow
runs-onlabels to adopt the new image this quarter. - Leader — Skip
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: If you use CodeQL in GitHub Actions, evaluate adopting the new dedicated workflow path to improve run-history clarity and accurate usage reporting — no deadline, but worth scheduling as routine pipeline hygiene.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: For teams running workloads on AWS Outposts with data residency requirements, this GA capability enables AMI and backup lifecycle workflows to keep snapshots fully on-Outpost without specifying an ARN manually — worth integrating into Outposts image-management processes this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you use S3 MRAP with CloudFront, you can now drop the Lambda@Edge workaround for SigV4a signing and let CloudFront handle OAC natively — plan to migrate existing custom auth header functions to simplify the architecture.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: EKS clusters created in 2018 have 10-year CAs now approaching expiry (~2028); audit cluster creation dates and schedule CA rotation this quarter — worker nodes must be replaced and external API clients updated to trust the successor CA before activation, which AWS will not do automatically.
- CI/CD — Learn: Pipelines that connect directly to EKS API servers (kubectl, Helm deploys, kubeconfig-based auth) qualify as external clients under the shared-responsibility model and would need CA trust updates during any rotation; no immediate action required but worth noting when rotation is scheduled by Platform.
- Leader — Skip
- Platform/SRE — Plan: GA capability that simplifies multi-team DynamoDB Streams IAM policy management via tag-based conditions; worth adopting this quarter if you manage access across multiple environments or teams on DynamoDB Streams.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: GA additions to CloudWatch pipelines reduce the need for custom log-transformation Lambda functions or external processors; evaluate replacing any bespoke RDS/XML parsing glue with these managed processors during the next observability stack review.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Teams using CloudWatch Centralization can now preserve cost, ownership, and compliance tags across accounts — worth enabling tag propagation on existing centralization rules to unlock IAM scoping and per-team cost attribution in Cost Explorer.
- CI/CD — Skip
- Leader — Learn: Tag propagation on centralized logs enables per-team observability cost attribution out of the box, which may inform how your org structures log ownership and FinOps reporting for multi-account environments.
- Platform/SRE — Plan: Now GA, these features let you right-size compute for workloads needing predictable single-threaded performance (e.g. licensed-per-core DBs) or reduced licensing costs; evaluate whether any production node pools or VM fleets would benefit from constrained-core configurations this quarter.
- CI/CD — Skip
- Leader — Plan: Constrained Cores can reduce per-core software licensing costs on Azure VMs; evaluate whether standardizing on constrained-core SKUs in the next planning cycle would yield material savings for licensed-per-core workloads.
- Signals: GA announcement
- Platform/SRE — Plan: If you run Tape or Volume Gateway for regulated workloads, you can now route FIPS-compliant traffic privately via PrivateLink instead of over the public internet; plan to create a FIPS interface VPC endpoint and re-activate gateways on software version 3.2.7 or later.
- CI/CD — Skip
- Leader — Learn: For organizations with compliance mandates (FedRAMP, HIPAA) using Storage Gateway, this removes a previous architectural constraint — FIPS traffic can now stay private — which may simplify audit scope for regulated workloads.
- Platform/SRE — Learn: Relevant for teams self-hosting GitLab — shallow and partial clones reduce server-side pack-building load, which compounds as agentic workloads increase clone frequency. No operational change required today, but useful context for capacity planning.
- CI/CD — Plan: Audit pipeline clone configurations and migrate to shallow (
--depth=1) or partial (--filter=blob:none) clones; benchmarks show up to 93% time and 98% disk reduction per clone. No hard deadline, but AI-agent-driven clone volume makes this a near-term efficiency project worth scheduling this quarter. - Leader — Skip
- Platform/SRE — Plan: Platform engineers managing Terraform-deployed AWS infra can now generate least-privilege IAM policies directly from plan files rather than hand-crafting them; worth integrating into the IaC workflow this quarter to reduce wildcard usage and policy drift.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: Useful new GitHub admin capability for scoping credential revocation by token type during incidents, but no infra dependency or deadline — worth knowing for incident runbooks.
- CI/CD — Plan: Scope incident response playbooks to leverage token-type revocation for PATs, OAuth tokens, and GitHub App tokens; audit current credential hygiene and update runbooks to use this targeted revocation before the next supply-chain incident.
- Leader — Skip
- Platform/SRE — Plan: App Engine Images→Cloud Run migration support is now GA for Java and Python — schedule evaluation this quarter if you operate App Engine standard workloads. Cloud SDK 581.0.0 flags a breaking change (removal of
gcloud beta services mcpcommands), but those were already no-ops so real pipeline impact is minimal; worth verifying before upgrading the SDK. - CI/CD — Skip
- Leader — Learn: The GA availability of the App Engine→Cloud Run migration path is a strategic signal if the org still runs App Engine workloads; no forced deadline, but it clarifies the long-term migration route Google is offering.
- Signals: GA announcement · breaking-change flagged
- Platform/SRE — Plan: New GA Azure App Service capability that enables lift-and-shift of on-premises or VM-hosted web apps to PaaS with minimal config changes; worth evaluating this quarter if the org runs any workloads on Azure VMs or bare metal that could be moved to a managed runtime.
- CI/CD — Skip
- Leader — Learn: Azure’s new managed migration path for web apps to App Service could shift build-vs-buy calculus for teams still running on VMs, but without pricing or SLA details in the announcement there’s no immediate strategic decision to make.
- Signals: GA announcement
- Platform/SRE — Learn: Kubeflow’s CNCF graduation signals broader enterprise adoption maturity; worth evaluating if your org runs ML workloads on Kubernetes, but no operational change required today.
- CI/CD — Skip
- Leader — Plan: CNCF graduation marks Kubeflow as a de-facto standard for cloud-native MLOps; evaluate whether to include it in the platform golden path for teams running AI/ML workloads this quarter.
- Platform/SRE — Plan: Useful GA capability for teams running large ephemeral fleets (ML training, event-driven); worth adopting in scale-down logic this quarter to reduce API call overhead and simplify fleet teardown scripts.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Rule hit counts are now enabled by default on AWS Network Firewall stateful rules, enabling detection of shadow, redundant, and unused rules — worth scheduling a policy audit this quarter to clean up firewall rule sets.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Three symlink/mount CVEs in the Docker engine (none KEV-listed, EPSS 0.00) warrant scheduling a patch to Moby 25.0.17 this sprint; also note that containerd 1.7 — vendored in this release — reaches EOL 2026-09-01, so any org running containerd 1.7 directly must plan a runtime upgrade within 15 days.
- CI/CD — Skip
- Leader — Skip
- Signals: containerd 1.7 reaches EOL in 15d (2026-09-01) · major release (25.0) · CVE-2024-40635 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-41567 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-41568 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Despite being a patch release, 2.3.4 ships a breaking change: checkpoint restore in CreateContainer is now disabled by default, requiring an explicit config opt-in. Also fixes a memory leak in the OOM watcher and binary protobuf shim corruption. Review workloads using CRIU/checkpoint restore before upgrading; schedule the upgrade this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: containerd 2.3 EOL 2028-04-30 · deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: containerd 2.2 reaches EOL on 2026-11-06 (81 days), so plan migration to a supported branch before then; also note this patch disables checkpoint restore in CreateContainer by default, which may break CRIU-based workloads that haven’t set enable_experimental_restore_via_create.
- CI/CD — Skip
- Leader — Skip
- Signals: containerd 2.2 reaches EOL in 81d (2026-11-06) · deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: v3.3.14 patches CLI secret-mask spoofing and fixes secrets leaking in last-applied-configuration annotations; CVE-2026-49978 (DOMPurify) is not KEV-listed and carries EPSS 0.00, so no emergency — schedule the upgrade within the quarter.
- CI/CD — Plan: Argo CD is explicitly in scope as the GitOps delivery layer; the server-side diff secret-mask spoofing fix could expose sensitive data in pipeline contexts — plan the upgrade to v3.3.14 this quarter.
- Leader — Skip
- Signals: Argo CD 3.3 supported · CVE-2026-49978 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: If your org builds custom AMIs or VM images with Packer, this GA release introduces native SLSA provenance that strengthens image supply-chain attestation — worth adopting this quarter as part of a platform hardening cycle.
- CI/CD — Plan: Packer v1.16.0 adds native SLSA provenance generation to machine image builds; if your pipelines include image baking steps, schedule an update to enable provenance output and integrate verification into the release gate.
- Leader — Learn: Packer’s native SLSA provenance support signals a maturing supply-chain posture for machine images, relevant to orgs building toward SLSA compliance — no immediate strategic decision required but worth factoring into policy planning.
- Platform/SRE — Plan: AKS operators can now collect native control plane metrics (API server, etcd, scheduler) through Managed Prometheus without custom exporters — worth scheduling adoption this quarter to close gaps in cluster observability.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Role manager can simplify onboarding new AWS services by auto-generating least-privilege starter roles, but teams with strict IaC discipline should evaluate whether console-created roles conflict with Terraform/CDK-managed IAM. Schedule a review of how role manager interacts with existing role governance before enabling org-wide.
- CI/CD — Skip
- Leader — Learn: Role manager lowers the barrier to correct IAM role setup for console-driven workflows, which may reduce misconfiguration risk across teams; worth noting as a governance tool but no immediate strategic decision required.
- Signals: GA announcement
- Platform/SRE — Plan: New GA capability lets EKS cluster admins tune scheduler, controller manager, and API server parameters — e.g. switching to MostAllocated bin-packing to reduce node count. Review the full parameter list and evaluate whether tuning fits your cluster’s resource-utilization or scaling goals this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: Reveals a blind spot in egress allowlist design: an allowed service (package proxy) can itself be pivoted through to reach the internet. Useful for rethinking network isolation architecture for sandboxes and evaluation environments, but no specific platform component or deadline to act on.
- CI/CD — Plan: The article explicitly names CI runners as sharing the same reachability structure as the exploited sandbox; egress allowlists that permit package proxies may allow lateral movement. Audit CI runner egress allowlists and ensure package proxy or dependency-resolution services on the allowlist cannot themselves serve as internet pivots.
- Leader — Learn: A responsibly disclosed AI agent security incident (OpenAI/Hugging Face) showing that agentic workloads can escape sandboxes through indirect paths, with real credential and data exposure. Relevant context for evaluating risk posture around AI agent adoption and agentic CI tooling, but no immediate vendor or strategic decision is forced.
- 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 — Skip
- CI/CD — Plan: If your repos still use legacy branch protection rules, schedule migration to GitHub rulesets using the new in-settings converter — rulesets offer better scalability and cross-repo policy management with no hard deadline yet.
- Leader — Skip
- Platform/SRE — Learn: CNB graduation signals broad production readiness for buildpack-based image builds; worth evaluating as a standardized, OCI-compliant alternative to Dockerfiles in the platform image pipeline.
- CI/CD — Plan: CNCF graduation makes Cloud Native Buildpacks a credible standard for container build steps in CI pipelines; evaluate adopting pack or a platform-native buildpack integration to replace Dockerfile-based builds this quarter.
- Leader — Learn: CNB reaching CNCF graduation reflects growing industry consensus around buildpack-based container standards; useful context for golden-path and build-vs-buy decisions but no immediate strategic action required.
- Platform/SRE — Learn: New GA capability for automating credential rotation without custom code; worth knowing for teams already using Secrets Manager managed external secrets, but no operational urgency.
- CI/CD — Plan: Teams using Jenkins or SonarQube with AWS Secrets Manager can now automate token rotation natively — schedule evaluation and adoption to reduce manual credential lifecycle work and lower the risk of stale tokens in pipelines.
- Leader — Skip
- Platform/SRE — Plan: This new GA feature unifies IAM role flexibility with IAM Identity Center federation, replacing the previous two-approach trade-off. Platform engineers managing AWS workforce access should evaluate adopting account access manager as their standard approach this quarter — no migration deadline exists, but it simplifies ongoing access architecture.
- CI/CD — Skip
- Leader — Learn: AWS now offers a third path for workforce federation that combines centralized user awareness with per-account IAM role granularity. Worth knowing as context when reviewing org-wide AWS access standards, but no licensing, pricing, or vendor-risk decision is triggered.
- Platform/SRE — Plan: R8a instances offer meaningful memory bandwidth and price-performance gains over R7a for memory-intensive workloads (databases, in-memory caches); worth evaluating for Canada Central production workloads during the next capacity planning cycle.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: The Cloud Run functions upgrade tool for migrating 1st-gen workloads to Cloud Run functions is now GA; schedule a migration project if your platform still runs 1st-gen functions to reduce future EOL exposure.
- CI/CD — Skip
- Leader — Plan: Cloud Hub’s App Topology API moves to usage-based billing on September 15, 2026; review org-wide App Topology usage now to quantify cost impact before the free daily allotment becomes the billing floor.
- Signals: GA announcement
- Platform/SRE — Plan: This GA feature replaces bespoke health-monitoring scripts for EC2 workloads and integrates with Auto Scaling recovery — worth evaluating this quarter to simplify the observability stack for any EC2-based services.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: Jenkins 2.576 ships multiple security fixes; review the 2026-08-05 security advisory and plan an upgrade of any self-hosted Jenkins controllers to this weekly build or wait for the next LTS incorporating these patches.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: Jenkins 2.568.2 carries a breaking-change flag; review the upgrade guide before updating the Jenkins controller to avoid pipeline regressions.
- Leader — Skip
- Signals: Jenkins 2.568 supported · breaking-change flagged
- Platform/SRE — Plan: Grafana 13.1.2 fixes CVE-2026-13438 in software Platform teams commonly operate; schedule the upgrade this sprint. No forced timeline — the CVE is not KEV-listed and no active exploitation is reported.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-13438 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Two regressions introduced in 29.7.0 — image pulls rejecting hardlink targets and file-permission failures on older kernels — are fixed in 29.7.2; if you upgraded to 29.7.x recently, schedule a patch to 29.7.2 to restore stable image pull behavior.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: ArgoCD runs as a control-plane component on managed clusters; a new GA minor release warrants scheduling a controller upgrade review this quarter to pick up any stability or feature improvements.
- CI/CD — Plan: ArgoCD 3.5.0 is a GA minor release directly in the deployment path; evaluate and plan adoption this quarter, particularly if you depend on any recently deprecated APIs or new sync/rollout features.
- Leader — Skip
- Signals: Argo CD 3.5 supported
- Platform/SRE — Plan: New GA minor release of a tool platform teams operate on-cluster; appset concurrency and configurable webhook jitter are operationally relevant improvements worth scheduling an upgrade to this quarter.
- CI/CD — Plan: SLSA Level 3 provenance for all container images and CLI binaries and new Source Integrity CLI support are meaningful supply-chain hardening steps worth adopting; plan to upgrade and enable provenance verification in deployment pipelines.
- Leader — Skip
- Signals: Argo CD 3.5 supported
- Platform/SRE — Plan: Relevant to any team using BYOIP prefixes on AWS: the new delegated RPKI automation eliminates manual ROA creation/renewal at the RIR, and the centralized dashboard surfaces hijacking risk via route overlap detection. Evaluate enabling this during the next IPAM configuration review cycle.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Learn: This expands the integration surface for enterprise GitHub accounts, which may be relevant when evaluating third-party tools that plug into GitHub for pipeline or workflow automation.
- Leader — Plan: Evaluate whether third-party GitHub Apps relevant to your toolchain (security scanners, compliance tools, IDP integrations) can now be deployed at the enterprise level, potentially simplifying governance and centralized app management.
- Platform/SRE — Plan: This GA simplification reduces friction for deploying resilient multi-Region identity access — if standing up a new IAM Identity Center organization instance, select the one-click multi-Region option rather than manually wiring KMS keys and Region replication. Existing instances are unaffected, so queue this for next new-instance or resilience-architecture work this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: Useful framing for understanding how unsanctioned AI tools introduce new attack surfaces into the platform layer, but no specific infrastructure action or deadline is present.
- CI/CD — Learn: Directly relevant to pipeline security thinking — AI extensions and agents in the build path are an emerging supply-chain risk worth evaluating, but no concrete deprecation, compromise, or deadline anchors an Act or Plan verdict.
- Leader — Plan: Shadow AI in delivery pipelines is a policy and governance gap that warrants adding AI tool usage to supply-chain standards and acceptable-use policy; schedule a review of which AI integrations teams are using in pipelines before the next security audit cycle.
- Platform/SRE — Plan: This GA release adds per-token inference cost attribution to OpenCost, directly addressing GPU cost visibility for platform teams running AI workloads on Kubernetes. Evaluate upgrading OpenCost to 1.121.0 this quarter if your clusters host inference workloads.
- CI/CD — Skip
- Leader — Plan: First GA implementation of per-token inference cost tracking in an open CNCF tool is a meaningful FinOps development for orgs with growing GPU spend; evaluate adopting OpenCost 1.121.0 as part of your AI cost attribution strategy this planning cycle.
- Platform/SRE — Plan: This GA expansion lets platform teams consolidate Kubernetes (ESO), Terraform/OpenTofu, and Vault CLI secrets into a single OpenBao-backed store — worth evaluating this quarter as a replacement for fragmented per-tool secret stores, with no forcing deadline yet.
- CI/CD — Learn: GitLab CI/CD secret support landed in v19.0 already; the new ESO and Terraform integrations are primarily platform-side — no pipeline changes required today, but the unified API surface is worth noting for future supply-chain design.
- Leader — Learn: The consolidated single-store model (one audit trail, one access model across Kubernetes, IaC, and pipelines) is worth tracking as a vendor-consolidation data point when revisiting secrets-toolchain standards, but no pricing or license forcing function exists yet.
- Platform/SRE — Plan: Teams running GitLab Self-Hosted in regulated environments can now configure the Duo AI Gateway to proxy through Privatemode’s confidential-compute backend — worth scheduling this quarter to evaluate setup and network path requirements alongside any existing compliance review.
- CI/CD — Learn: The prospect of GitLab Duo Agent Platform driving multi-step agentic flows as native CI jobs is a meaningful design shift to track, but there are no pipeline migrations or deprecations to act on today.
- Leader — Plan: For regulated orgs blocked from AI coding tools by IP or compliance constraints, this materially changes the vendor-risk calculus — evaluate Privatemode as a compliant model-provider path for GitLab Duo during the next planning cycle before competitors further compound their AI productivity lead.
- Platform/SRE — Plan: If you run MSK Provisioned clusters, enable Authorizer Log Delivery to route denied-access events (with client IP and API) to CloudWatch, S3, or Firehose — useful for security auditing and troubleshooting auth issues at no added cost.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA ECS capability lets you right-size GPU containers (1/8, 1/4, or 1/2 of an L4 GPU) on G6f instances, with CloudWatch GPU metrics and automatic health monitoring included. Evaluate this quarter if you run ECS-based AI inference or rendering workloads where full-GPU allocation is wasteful.
- CI/CD — Skip
- Leader — Learn: Fractional GPU scheduling in ECS reduces the cost floor for small-model inference and GPU experimentation workloads; worth factoring into GPU cost optimization reviews if the org runs AI workloads on ECS.
- Platform/SRE — Skip
- CI/CD — Plan: If your org uses GitHub code scanning default setup, evaluate adopting the new github-codeql-config-file repository property to standardize CodeQL scan behavior across repos without per-repo overrides.
- Leader — Plan: This enables centralized enforcement of code scanning standards across the org’s repositories — worth incorporating into the golden path or security policy for teams already on GitHub Advanced Security.
- Platform/SRE — Plan: Two GA releases are worth scheduling for adoption: native OTLP metric ingestion into Cloud Monitoring via the Telemetry API (evaluate replacing or supplementing existing collector pipelines), and Cloud SQL for MySQL performance capture with configurable thresholds for long-running transactions and new triggers like CPU, memory, and lock waits.
- CI/CD — Skip
- Leader — Learn: The Telemetry API GA enables native OTLP ingestion into Cloud Monitoring, which may affect the build-vs-buy decision for third-party observability tooling on GCP; no strategic decision is required yet.
- Signals: GA announcement
- Platform/SRE — Plan: TCPRoute and UDPRoute are now stable in the v1 API, making portable L4 routing viable for production workloads like databases, DNS, and VoIP. If you’re already using experimental Gateway API resources, audit for the new gateway.networking.x-k8s.io API group separation to avoid breakage on upgrade.
- CI/CD — Skip
- Leader — Learn: Gateway API continues maturing as the unified Kubernetes networking standard; L4 GA coverage strengthens the case for standardizing on it as the org’s golden-path ingress model over implementation-specific CRDs.
- Platform/SRE — Skip
- CI/CD — Plan: If a GitLab-to-GitHub migration is on the roadmap, GEI reaching GA means self-serve tooling is now available for scoping the pipeline migration project.
- Leader — Plan: If your org is evaluating consolidating from GitLab to GitHub Enterprise Cloud, the GA of self-serve migration tooling removes a key friction point worth including in the next planning cycle.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: If pipelines use CodeQL for code scanning on Swift or Kotlin codebases, upgrade to 2.26.2 to gain language-version coverage for Swift 6.3.3 and Kotlin 2.4.10; no deadline, but worth scheduling this quarter.
- Leader — Skip
- Platform/SRE — Plan: New Azure Gen2 VM and VMSS deployments now automatically get Secure Boot and vTPM enabled; audit IaC templates and any custom images for Secure Boot compatibility to avoid silent failures on next VM provisioning.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Learn: This GA tool auto-creates PRs/MRs with validated code fixes from technical debt analysis connected to GitHub, GitLab, and Bitbucket — worth evaluating if the team wants automated remediation integrated into their pipeline workflow, but no pipeline change is required today.
- Leader — Plan: Evaluate AWS Transform as a platform-level technical debt and modernization tool for standardizing debt management across teams; assess whether its agentic remediation and scheduling capabilities fit the org’s golden-path tooling this quarter.
- Signals: GA announcement
- Platform/SRE — Plan: If you run high-throughput SQS-to-Lambda pipelines that previously required splitting workloads across multiple ESMs, this GA increase to 10,000 pollers and 100,000 concurrent invocations is worth consolidating architecture this quarter.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: Patch includes dependency updates for CVE-2026-56852 and GHSA-hrxh-6v49-42gf (neither KEV-listed nor actively exploited) plus a PromQL SIGBUS crash fix on full disks; schedule an upgrade to 3.13.2 this maintenance cycle.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-56852 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Two confirmed regressions patched: image pulls failing for layers with implicit parent directories, and CopyToContainer rejecting valid symlink paths like /var/run. Schedule an upgrade to 29.7.1 if running 29.7.x in production.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Upgrade Docker Engine to v29.7.0 to patch CVE-2026-17106 (go-archive archive-traversal fix) and resolve two daemon panic bugs in container network cleanup paths; the CVE is not KEV-listed so no hard deadline, but schedule this within the current sprint.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-17106 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: Cilium 1.20.0 is a substantial GA minor release for a core CNI component; before upgrading, audit whether your cluster uses legacy Mutual Authentication, Envoy Go extensions, Kafka-aware policies, the cilium.io/v2alpha1 CiliumNodeConfig API, libnetwork, or custom CNI configs — all require migration steps per the upgrade guide. No forced-upgrade deadline exists, so schedule evaluation this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Grafana Agent Observability is now GA on Grafana Cloud, offering structured monitoring for LLM agent behavior, prompt lineage, and scaling. Platform teams operating agent workloads should evaluate adopting it this quarter as a dedicated layer alongside their existing Grafana stack.
- CI/CD — Skip
- Leader — Learn: Grafana’s GA release of purpose-built agent observability tooling reflects a maturing category for AI workload monitoring; useful framing for leaders deciding where to invest observability capabilities as agent-based products scale.
- Signals: GA announcement
- Platform/SRE — Plan: A semver major bump in a provider teams rely on for Azure IaC signals likely breaking changes; schedule a migration from AzureRM 4.x to 5.0 this quarter, validating existing configurations against the new Resource Provider registration behavior and opt-in preflight validation before upgrading production workspaces.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement · major release (5.0)
- Platform/SRE — Skip
- CI/CD — Plan: Teams that publish npm packages via their release pipelines should review the new dual-use metadata requirement to ensure compliance before enforcement begins; no hard deadline surfaced in the item, so schedule this in the next pipeline audit cycle.
- Leader — Learn: npm’s automated publish-time scanning strengthens the ecosystem’s supply-chain posture; worth noting as a positive signal when reviewing org-wide software supply-chain policy, but no leadership decision is required now.
- Platform/SRE — Skip
- CI/CD — Plan: GitHub now holds potentially malicious workflow runs for review in public repositories; audit your org’s Actions approval settings and ensure maintainers understand how to review held runs before merging external contributions.
- Leader — Learn: GitHub’s new default protection against credential-stealing workflow attacks reduces supply-chain risk for orgs using public repos; worth noting as a positive vendor-risk signal when assessing GitHub Actions dependency.
- Platform/SRE — Plan: Cloud SDK 578.0.0 makes –auto-commit the default for gcloud database-migration seed/convert/import-rules commands; audit any automation or runbooks that call these operations and add –no-auto-commit explicitly before upgrading the SDK.
- CI/CD — Plan: If pipelines invoke gcloud database-migration commands, upgrading to Cloud SDK 578.0.0 silently changes commit behavior; pin the SDK version or add –no-auto-commit flags before the next runner/image update pulls this version in.
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Skip
- CI/CD — Plan: Enable or verify Dependabot alerts are active across your repos to benefit from the expanded OpenSSF malicious-package coverage; no deadline, but this materially improves supply-chain detection in your dependency pipeline.
- Leader — Plan: Broader malware signal coverage from OpenSSF integration strengthens your software supply-chain posture — confirm Dependabot alerts are enabled org-wide as a policy standard this quarter.
- Platform/SRE — Plan: GA resource placement in Fleet Manager enables centralized policy-driven workload distribution across multiple AKS clusters, worth evaluating this quarter if you operate a multi-cluster Azure environment.
- CI/CD — Skip
- Leader — Learn: Fleet Manager’s GA multi-cluster resource placement matures Azure’s managed Kubernetes offering and may influence build-vs-buy decisions around homegrown multi-cluster orchestration tooling.
- Signals: GA announcement
- Platform/SRE — Plan: For EKS clusters in air-gapped or strict-egress VPCs, this GA capability enables IRSA token validation without internet access — evaluate adding the com.amazonaws.
.oidc-eks VPC interface endpoint to your network baseline this quarter. - CI/CD — Skip
- Leader — Skip
- 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
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: If your org uses GitHub Copilot, this GA policy control lets you enforce centralized governance over the Copilot desktop app and cloud agent — evaluate rolling it into your Copilot access standards this quarter.
- Platform/SRE — Skip
- CI/CD — Plan: GitHub now holds unproven workflows pending approval on public repos — review your repository settings and approval workflows to ensure this protection is enabled and fits your release process.
- Leader — Learn: A new GitHub platform-level control targeting supply chain attacks via compromised credentials; worth noting as a defense-in-depth signal for orgs that rely on GitHub Actions for public repositories.
- Platform/SRE — Plan: New GA Neptune capability that replaces static ARN enumeration in IAM policies with attribute-based cluster access using resource and principal tags; plan to adopt TBAC if you operate multiple Neptune clusters in shared VPC environments to enforce team and environment isolation.
- CI/CD — Skip
- Leader — Learn: Neptune now supports attribute-based access governance across clusters via IAM tags, useful context for organizations running Neptune at scale, but no strategic, licensing, or cost decision is triggered.
- Platform/SRE — Plan: Platform engineers running OpenTofu should upgrade to 1.12.5 to address the ECH handshake privacy leak (server hostname de-anonymization via passive observation) and the implicit-move provider state bug; no KEV listing or active exploitation reported, so no hard deadline, but this should be included in the next IaC toolchain update cycle.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: A security fix for an ECH pre-shared key identity leak in OpenTofu v1.11.x warrants upgrading to v1.11.13; no KEV listing or active exploitation reported, so this is a planned patch rather than an emergency — schedule the upgrade this sprint.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: etcd backs every Kubernetes control plane, and a breaking change in a patch release is unusual — review the v3.7.1 CHANGELOG and upgrade guide before applying this update to any cluster, and validate in a non-production environment first. No hard deadline exists, but the breaking-change flag makes this a planned, careful upgrade rather than routine patching.
- CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: etcd is the Kubernetes control plane’s backing store — a breaking-change flag in even a patch release means reviewing the upgrade guide before rolling this out to production clusters. No deadline is given, but operators should validate against their environment this quarter before routine patching.
- CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: etcd backs every Kubernetes control plane, and a breaking-change flag on a patch release is unusual — review the CHANGELOG and upgrade guide before rolling this out to clusters; no hard deadline, but unreviewed breaking changes in a core datastore warrant a planned change window rather than routine rollout.
- CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: Teams using IP allowlisting to permit Grafana Cloud traffic must migrate from legacy per-product endpoints (JSON, txt, DNS) to the new unified Allowlist API before January 31, 2027, when the old formats stop being maintained; schedule the allowlist automation update and test before the deadline.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run EC2 Dedicated Hosts or Mac Instances for isolation rather than BYOL, you can now create Host Resource Groups without the AWS License Manager self-managed license prerequisite, simplifying the provisioning workflow. Review and update any Terraform/IaC automation that currently creates SMLs solely to satisfy the HRG requirement.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Airflow 2.11.2 on MWAA is a maintenance release with security patches to the webserver and task execution layers, plus enhanced secrets masking in logs — worth scheduling an environment upgrade this quarter if you run MWAA in production. No forced-upgrade deadline is present in the signals.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: I8ge instances (Graviton4, 3rd-gen Nitro SSDs, up to 120TB NVMe) are now GA in two more regions — worth evaluating as a replacement for Im4gn or I3en nodes in storage-heavy workloads this quarter.
- CI/CD — Skip
- Leader — Learn: New storage-optimized Graviton4 instance family expanding regionally; relevant context for future Graviton migration planning or FinOps reviews comparing storage-intensive workload costs.
- Signals: GA announcement
- Platform/SRE — Plan: HCP Terraform and Terraform Enterprise now include workspace and Stacks restore features, which are relevant to DR and state-recovery planning for teams standardized on either product; evaluate whether these capabilities close gaps in your current runbooks.
- CI/CD — Skip
- Leader — Learn: HashiCorp is expanding HCP Terraform’s resilience and governance surface; useful context for teams standardized on the product when assessing vendor roadmap health, but no strategic decision is forced here.
- Platform/SRE — Plan: GA feature that reduces cross-AZ data transfer costs and latency for ECS Service Connect; existing services need a one-time redeployment to activate it. Schedule the redeployment across affected ECS services this quarter to capture the cost and latency benefit.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: ALB logs are now a first-class CloudWatch vended log type, enabling Logs Insights queries, metric filters, and Live Tail for load balancer traffic without custom shipping pipelines; evaluate adopting telemetry enablement rules to standardize coverage across accounts, noting the per-GB vended log cost vs. free S3 delivery.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: Grafana Cloud now supports label-based cost attribution (e.g., team, env) across metrics, logs, traces, k6, and Synthetic Monitoring — useful context for platform teams that want to support internal showback models, but no migration or deadline is involved.
- CI/CD — Skip
- Leader — Plan: Evaluate enabling Grafana Cloud cost attribution labels this quarter if the org needs chargeback or showback across teams; the new k6 and Synthetic Monitoring coverage makes this a more complete FinOps lever for observability spend.
- Platform/SRE — Plan: GDC for VMware 1.35.300-gke.87 (Kubernetes 1.35.3) and 1.34.700-gke.93 (Kubernetes 1.34.7) are available for download; if running 1.34, note its EOL is 2026-10-27, so schedule an upgrade to 1.35 this quarter before that deadline.
- CI/CD — Skip
- Leader — Skip
- Signals: Kubernetes 1.35 EOL 2027-02-28 · Kubernetes 1.34 EOL 2026-10-27
- Platform/SRE — Plan: New GA capability that changes how you’d architect EKS node pools for GPU/HPC workloads — evaluate EFA-only interfaces (no IP consumption) and placement group strategies for distributed training or high-availability production services this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA capability removes the CloudTrail-parsing workaround for secret rotation events; evaluate adding EventBridge rules this quarter to auto-refresh credential caches or trigger service restarts on rotation, reducing the lag window between rotation and downstream adoption.
- CI/CD — Learn: Could inform future pipeline designs that need to react to secret rotation (e.g., invalidating cached build credentials), but no current pipeline change is required and no deprecation is introduced.
- Leader — Skip
- Platform/SRE — Plan: New GA NLB capability worth evaluating this quarter for teams running dual-stack workloads: a single NLB can now route IPv4 and IPv6 clients to same-family targets without protocol translation or a second load balancer. Audit existing dual-stack NLB deployments and update Terraform/IaC to add listener rules where protocol translation is currently causing IP preservation issues.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run Lambda durable functions in regulated industries, schedule adoption of CMK encryption to meet data governance requirements — no deadline, but this is a concrete security posture change worth queuing this quarter.
- CI/CD — Skip
- Leader — Learn: Lambda durable functions now offers CMK support, closing a compliance gap for financial services and healthcare workloads; relevant context if evaluating serverless for regulated data.
- Platform/SRE — Plan: The updated ToS may restrict how the Terraform Registry can be consumed, particularly by tooling or automation that competes with or mirrors registry content. Review current Terraform and provider-download patterns against the new terms and evaluate whether a migration to OpenTofu or a self-hosted registry should be scoped this quarter.
- CI/CD — Learn: Pipelines that pull Terraform providers and modules via the public registry could be indirectly affected if the new ToS introduces usage restrictions on automated clients; worth monitoring, but no concrete pipeline action is required yet.
- Leader — Plan: A ToS change on a registry that most Terraform-standardized orgs depend on is a direct vendor-risk signal; evaluate whether current registry consumption falls under any newly restricted terms and assess OpenTofu as a contingency before any enforcement timeline is announced.
- Platform/SRE — Plan: Docker removing the cost barrier for hardened, minimal base images makes it practical to standardize on them across cluster workloads, reducing CVE surface without budget justification. Evaluate adopting Docker Hardened Images as the default base-image standard in your next quarterly planning cycle.
- CI/CD — Plan: Hardened base images are directly relevant to build-time and artifact supply-chain security; with the free tier now available, it’s worth scheduling a migration of pipeline build images and application Dockerfiles to hardened variants as a supply-chain hardening step.
- Leader — Learn: Docker making a previously premium security feature free reshapes the container security tooling landscape and is useful context for evaluating whether to formalize a hardened-image standard in the golden path, but no immediate strategic decision is required.
- Platform/SRE — Plan: SQL Server 2025 is now GA on RDS; teams operating SQL Server workloads should evaluate an engine upgrade to gain Standard Edition capacity increases (up to 32 cores, 256 GB buffer pool) and Resource Governor, previously Enterprise-only — no deadline, but a meaningful capability shift worth scheduling this quarter.
- CI/CD — Skip
- Leader — Learn: SQL Server 2025 introduces a new free Dev-SE edition and significant Standard Edition capacity/feature improvements that could reduce Enterprise licensing costs; worth noting for next SQL Server licensing review, but no immediate strategic decision is forced.
- Platform/SRE — Plan: This GA feature surfaces previously opaque ECS service-side deployment events — state transitions, circuit-breaker rollbacks, Managed Daemon updates — directly into CloudWatch, S3, or Firehose. Platform teams running ECS should evaluate opting in at the cluster level to reduce MTTR on deployment incidents without waiting on AWS Support.
- CI/CD — Learn: ECS Action Logs expose service-side operations that can help diagnose failures in pipeline-triggered deployments, but no pipeline changes are required — this is an opt-in ECS console/CloudWatch feature, not a build or artifact system change.
- Leader — Skip
- Platform/SRE — Learn: A community module for self-hosted GitHub Actions runner autoscaling on AWS; worth evaluating if teams are self-hosting runners, but no deadline or GA milestone signals a required change.
- CI/CD — Plan: If cost or throughput is a pain point with GitHub-hosted runners, this Terraform module offers a path to autoscaled self-hosted runners on AWS — worth scheduling an evaluation this quarter.
- Leader — Skip
- Platform/SRE — Plan: Oracle’s enterprise-scale migration validates OpenTofu as production-ready; teams running Terraform under the BUSL license should schedule an evaluation of OpenTofu as a drop-in replacement within the next planning cycle.
- CI/CD — Skip
- Leader — Plan: A major cloud vendor publicly switching to the OpenTofu fork is a clear signal that the fork has enterprise momentum; leaders standardized on Terraform should put an OpenTofu migration evaluation on the roadmap to reduce BUSL licensing risk before it becomes a contractual concern.
- Platform/SRE — Skip
- CI/CD — Plan: New GA GitHub feature worth evaluating for pipeline quality gates; assess whether Code Quality checks should be integrated into existing GitHub Actions workflows this quarter.
- Leader — Learn: GA release of a GitHub-native code quality tool that may reduce the need for third-party static analysis seats; worth tracking as a build-vs-buy data point at next toolchain review.
- Signals: GA announcement
- Platform/SRE — Plan: If you run memory-intensive workloads (PostgreSQL, NGINX, ML inference) in EU Stockholm or Zurich, evaluate migrating to R8i for up to 30–60% workload-specific gains; no deadline, so schedule as a cost-performance optimization this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: New GA CloudWatch feature ingesting OpenTelemetry metrics from coding agents; no infrastructure changes required, but platform engineers who own the observability stack should note it as a new dimension of telemetry available alongside existing operational data.
- CI/CD — Skip
- Leader — Plan: Directly addresses AI coding tool ROI governance — token spend, commit throughput, PR velocity, and cost-per-model comparisons; evaluate enabling Coding Agent Insights this quarter to inform decisions on expanding or right-sizing AI tool access across teams.
- Platform/SRE — Plan: This GA feature lets you reduce CloudTrail network activity event volume and cost by scoping logging to untrusted or access-denied identities on VPC endpoints — a concrete improvement for data perimeter monitoring. Update your CloudTrail advanced event selectors this quarter to filter trusted IAM roles and cut noise on VpceAccessDenied events.
- CI/CD — Skip
- Leader — Learn: This feature enables selective CloudTrail logging that can meaningfully reduce ingestion costs for high-volume VPC endpoint environments, relevant for FinOps conversations around AWS audit logging spend — no strategic decision required now.
- Platform/SRE — Plan: If your pipelines use pulumi/actions or pulumi/action-install-pulumi-cli, both have major version bumps (v6→v7, v1→v2) that likely include breaking changes; audit your workflow files and update action refs this quarter.
- CI/CD — Plan: pulumi/actions jumped v6→v7 and pulumi/action-install-pulumi-cli jumped v1→v2 — major bumps that may break existing pipeline steps; review release notes for both actions and update workflow references before Renovate auto-merges cause unexpected failures.
- Leader — Skip
- Platform/SRE — Plan: v1.39.0 patches several CVEs across ext_authz, ext_proc, gRPC stats, and HTTP/2/HTTP/3 DoS vectors, but none are KEV-listed and EPSS is 0.00 — no hard deadline. Plan the upgrade this quarter, and validate the breaking TLS enforcement change and OpenTelemetry sampling behavior shift in staging before rolling to production.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found) · breaking-change flagged · CVE-2026-47204 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-47205 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-47207 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: Five CVEs fixed in Docker Engine including a command injection via git bundle checkout and a directory traversal that can wipe /tmp — no KEV listing or known active exploitation, but the severity warrants scheduling an upgrade to 29.6.2 this sprint.
- CI/CD — Plan: If Docker Engine runs on self-hosted CI runners or build hosts, the git-bundle command injection (CVE-2026-15793) and local-source upload bypass (CVE-2026-15789) are directly relevant to build-time workloads; plan to update runner environments to Docker 29.6.2.
- Leader — Skip
- Signals: CVE-2026-15788 — CISA KEV: not listed, EPSS n/a · CVE-2026-15789 — CISA KEV: not listed, EPSS n/a · CVE-2026-15791 — CISA KEV: not listed, EPSS n/a
- Platform/SRE — Plan: If running Cilium 1.19.x, this patch fixes a regression that briefly drops established pod connections during agent restart or upgrade; no deadline or KEV, but the availability impact warrants scheduling an upgrade to 1.19.6 this sprint.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Two notable bug fixes: a regression that prevents Cilium from starting in kvstore mode with KPR enabled when etcd is behind a Kubernetes service, and incorrect policy denials for L7 load-balanced services on remote identity changes. If running Cilium 1.18.x in either of these configurations, schedule the patch update this sprint.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Teams running Backstage need to audit OAuth redirect URI allowlist patterns (wildcards no longer cross host/path boundaries), validate config schema imports that may now fail to load, and migrate any MCP clients off the removed SSE transport to the Streamable HTTP endpoint before upgrading to v1.53.0.
- CI/CD — Skip
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: Teams running OpenSearch Service domains or serverless collections with Dashboards tenants and saved objects can now migrate to the new OpenSearch UI without manual recreation; worth scheduling as a low-risk migration this quarter to reduce legacy UI dependency.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: A new GA security capability for AKS clusters using Azure Files NFS v4.1 volumes via the CSI driver — worth evaluating this quarter for workloads with data-in-transit compliance requirements. Review existing PersistentVolume configurations and enable EiT where encryption mandates apply.
- CI/CD — Skip
- Leader — Learn: This GA feature expands available encryption controls on AKS-backed storage, which may inform security standards or compliance posture for teams running NFS workloads on Azure, but no strategic decision is forced.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: Custom Flows are now GA in GitLab 19.2, enabling event-triggered, AI-driven multi-step pipeline sequences (e.g., analyze failure → generate fix → commit → notify). Teams on GitLab should evaluate whether encoding trusted delivery sequences as Flows reduces manual handoffs and pipeline runbook debt.
- Leader — Learn: GitLab’s agentic flow model represents a meaningful shift in how AI is integrated into the delivery lifecycle — moving from single-turn chat to orchestrated, human-approved sequences. Worth tracking as input to dev-platform strategy and AI tooling evaluation, but no strategic decision is forced by this release.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: Enterprises standardized on GitHub Enterprise Cloud can now automate VSS seat assignments via REST API, enabling programmatic license auditing and allocation at scale — worth scheduling into the licensing management workflow.
- Platform/SRE — Plan: Apigee X instances below 1-17-0-apigee-10 with maintenance windows configured will be auto-updated within 7–21 days of July 16; verify now that your instances don’t carry the DNS misconfiguration (known issue 445936920) or a dependency on the removed Apigee Java Library, as either will block the automatic update. Cloud KMS ML-DSA and SLH-DSA post-quantum signing algorithms are now GA — add PQC key-management evaluation to this quarter’s platform roadmap.
- CI/CD — Skip
- Leader — Learn: Google Cloud KMS now offers post-quantum signing algorithms (ML-DSA, SLH-DSA families) in GA — a signal that PQC migration timelines are becoming concrete and worth factoring into the org’s long-term cryptographic standards and compliance planning.
- Signals: GA announcement
- Platform/SRE — Plan: Teams using AFT to manage multi-account AWS environments should evaluate enabling
aft_customization_triggers = ["account_move"]this quarter to eliminate manual re-application steps and reduce compliance drift when accounts change OUs. No deadline, but the tighter logging bucket controls and enterprise-scale improvements are also worth reviewing alongside the opt-in. - CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: New secret types are now auto-detected in repo scans; review your secret scanning policy to ensure newly covered credential types (Resend, APIclub) are included in alerting and rotation workflows.
- Leader — Skip
- Platform/SRE — Plan: New Docker 29 installs default to the containerd image store rather than the classic overlay store, which changes image management behavior. Audit IaC and provisioning scripts that stand up Docker nodes to verify compatibility with the new default before rolling out Docker 29 to new infrastructure.
- CI/CD — Plan: Ephemeral CI runners provisioned fresh on Docker 29 will silently get containerd-backed image storage, which can alter layer-caching behavior and multi-platform build handling. Test existing build and image-export workflows against the new default before adopting Docker 29 runner images.
- Leader — Skip
- Platform/SRE — Plan: If you use AWS DRS for EC2 workloads, enabling this feature can meaningfully shrink your RTO with no added cost — evaluate enabling it account-wide or per server during your next DR review.
- CI/CD — Skip
- Leader — Learn: A no-cost RTO improvement of up to 65% on EC2 disaster recovery is worth noting when reviewing reliability targets and DR posture with engineering leadership.
- Platform/SRE — Plan: Teams running Amazon MQ RabbitMQ M7g cluster deployments on version 4.2+ can now right-size storage independently of instance type; evaluate current broker storage allocations and adjust during the next planned maintenance window.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA capability that can eliminate the need to export verbose logs to S3 or filter them for cost reasons — evaluate enabling account-level intelligent tiering this quarter to simplify your observability stack and reduce log storage spend.
- CI/CD — Skip
- Leader — Plan: This changes the unit economics of CloudWatch log retention, making it viable to keep high-volume logs natively rather than running export pipelines to cheaper storage; include in the next FinOps/observability cost review cycle.
- 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)
- Platform/SRE — Skip
- CI/CD — Plan: New GA endpoints let teams manage secret scanning custom patterns as code, enabling IaC-style enforcement of scanning policies across repos; schedule adoption as part of supply-chain hardening this quarter.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: GitHub’s AI-powered security detections now surface on PRs for languages CodeQL doesn’t cover — worth enabling to broaden supply-chain and vulnerability coverage in existing GitHub Actions workflows.
- Leader — Learn: Expanded AI security coverage on PRs broadens GitHub’s appeal as a unified code-security platform, relevant if evaluating whether GitHub Advanced Security covers the org’s language portfolio.
- Platform/SRE — Plan: gcloud SDK 576.0.0 changes
gcloud storage rsyncto decompress gzip downloads by default, which can silently break any operational scripts relying on the previous behavior; audit usage and add--do-not-decompressor pin SDK version before upgrading. The bundled Python update for CVE-2026-34182 (EPSS 0.00, not KEV) adds low-urgency motivation to upgrade. - CI/CD — Plan: If pipelines invoke
gcloud storage rsyncto pull artifacts, the 576.0.0 default-decompress behavior change will alter what lands in the workspace; pin the gcloud SDK version or add--do-not-decompressbefore rolling out the upgrade across runners. - Leader — Learn: BigQuery conversational analytics now carries HIPAA compliance support, broadening Gemini-in-BigQuery eligibility for regulated-industry workloads — worth factoring into GCP data platform strategy for healthcare or other compliance-sensitive verticals.
- Signals: GA announcement · breaking-change flagged · CVE-2026-34182 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Plan: New GA capability that consolidates CloudFront Function decisions (A/B variants, auth outcomes, routing) directly into access log records, eliminating cross-system correlation with CloudWatch Logs. Worth adopting in existing CloudFront Functions this quarter by replacing or augmenting console.log() with cf.logCustomData().
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: New GA capability that auto-discovers AI workloads (Bedrock, SageMaker, EC2, ECR) via Config, Inspector SBOM, and GuardDuty DNS telemetry — worth enabling this quarter for teams running AI workloads to close the visibility gap before it becomes a compliance issue.
- CI/CD — Skip
- Leader — Learn: Signals that AWS is building central AI governance tooling; relevant for leaders setting security standards around AI deployments, but no forced decision or pricing change — shapes thinking on AI risk posture policy rather than requiring action now.
- Platform/SRE — Plan: This GA capability removes the per-Region Lambda-managed storage quota for teams running large function/layer footprints; evaluate adopting
S3ObjectStorageMode=REFERENCEthis quarter for deployments approaching the old 75GB ceiling, and note the default limit has already been raised to 300GB for all accounts. - CI/CD — Skip
- Leader — Learn: Cost impact is neutral-to-positive (standard S3 rates replace implicit Lambda storage overhead) with no forced migration, but worth flagging to platform teams running high function counts so they can evaluate whether S3-backed storage fits their existing artifact management posture.
- Platform/SRE — Plan: Teams running I/O-intensive workloads (databases, etc.) on AWS DRS should evaluate setting an EBS initialization rate on DRS launch templates to reduce time-to-full-performance during recovery drills — no deadline, but worth scheduling as a DR configuration review this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Prometheus is core observability infrastructure; upgrade to v3.5.5 to patch CVE-2026-53606 in the UI’s sanitize-html dependency. Exploitation risk is low (EPSS 0.00, not KEV-listed), so this is routine patching rather than an emergency.
- CI/CD — Skip
- Leader — Skip
- Signals: CVE-2026-53606 — CISA KEV: not listed, EPSS 0.00
- Platform/SRE — Skip
- CI/CD — Plan: Two deserialization restrictions (COWL/PersistedList and Object fields by default) are meaningful security hardening in the Jenkins controller; review whether your instance is affected and schedule an upgrade within your normal maintenance window.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: Jenkins 2.568.1 carries a breaking-change flag; review the upgrade guide before updating your Jenkins controller to avoid pipeline or configuration regressions.
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: Flux v2.9.2 fixes a real regression (Kustomization openapi.path URL reconcile failure) introduced in v2.9.1 — worth scheduling an upgrade this sprint if you use that feature. Also note Flux 2.6 passed EOL on 2026-06-30; if still running it, upgrade to 2.7+ now.
- CI/CD — Skip
- Leader — Skip
- Signals: Flux 2.9 supported · Flux 2.7 supported · Flux 2.6 is past EOL (2026-06-30, 13d ago)
- Platform/SRE — Plan: Fixes a meaningful regression where Kustomizations with post-build substitution enabled could corrupt Flux CRD schemas containing ${…} sequences; also patches a SOPS .ini decryption bug and a dry-run apply error. Schedule an upgrade to v2.9.1 this sprint, prioritizing clusters that use post-build variable substitution — no hard deadline, but the CRD corruption impact in affected environments is production-visible.
- CI/CD — Skip
- Leader — Skip
- Signals: Flux 2.9 supported · Flux 2.7 supported · Flux 2.6 is past EOL (2026-06-30, 13d ago) · breaking-change flagged
- Platform/SRE — Plan: etcd is a critical Kubernetes control-plane component; v3.7.0 carries flagged breaking changes requiring review of the upgrade guide before any cluster upgrade. Plan the migration this quarter — no forced deadline in the signals, but breaking changes mean this needs a scoped project, not a routine bump.
- CI/CD — Skip
- Leader — Skip
- Signals: breaking-change flagged
- Platform/SRE — Plan: etcd is the Kubernetes control-plane backing store, so any new minor release warrants a changelog review for deprecations, API changes, or breaking behavior before scheduling an upgrade cycle; no deadline or CVE signals are present to force earlier action.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: This GA major release changes how Tempo is deployed at scale — removing the RF3 requirement reduces storage overhead and the new Kafka-compatible architecture decouples read/write paths. Teams running Tempo should schedule an upgrade evaluation this quarter to assess the operational and cost impact.
- CI/CD — Skip
- Leader — Learn: The RF3 removal and new architecture lower the infrastructure cost of running distributed tracing at scale, which is a useful data point if Tempo is part of the observability standard — but no strategic decision is forced by this release.
- Signals: GA announcement · major release (3.0)
- Platform/SRE — Plan: Grafana 13.1 ships GA improvements to Git Sync — GitHub App auth, GitLab/Bitbucket support, and in-place provisioned-folder imports — that meaningfully advance dashboard-as-code workflows for teams already on Grafana. Evaluate adopting these features this quarter; EOL for 13.1 is 2027-03-20, so no immediate upgrade pressure.
- CI/CD — Skip
- Leader — Learn: Grafana’s investment in native GitOps (Git Sync) and AI-assisted querying across more data sources signals where observability tooling is heading; useful context for evaluating observability-as-code as an org standard, but no strategic decision is forced by this release.
- Signals: Grafana 13.1 EOL 2027-03-20 · GA announcement
- Platform/SRE — Plan: If running memory-intensive or high-network-throughput workloads in ap-northeast-1, eu-central-1, or eu-west-1, evaluate whether R8i-family instances offer a cost/performance improvement over existing R6i deployments — up to 43% better compute per vCPU and highest-in-class EBS/network bandwidth are meaningful for caching, NoSQL, or analytics tiers.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: If pipelines run CodeQL scanning on Kotlin 2.4.0 codebases, upgrade to CodeQL 2.26.0 this quarter to maintain scan coverage; the new AI prompt injection queries are worth enabling if building LLM-integrated apps.
- Leader — Skip
- Platform/SRE — Learn: Teams using CDKTF for IaC should read this discussion to gauge whether HashiCorp/IBM intends to maintain it long-term; no deprecation date in signals, so no action required now.
- CI/CD — Skip
- Leader — Plan: Against the backdrop of HashiCorp’s BSL relicensing and IBM acquisition, a high-signal HN discussion on CDKTF’s direction is a prompt to evaluate whether to continue standardizing on CDKTF or assess alternatives like OpenTofu CDK this planning cycle.
- Platform/SRE — Learn: Useful context for teams running Volkov Labs BI plugins on Grafana: the maintenance window is extended and Grafana 13 / React 19 compatibility is done, but no action is required now and the post-2026 path remains undefined.
- CI/CD — Skip
- Leader — Plan: If the org is standardized on Volkov Labs BI plugins, the finite maintenance window expiring at end of 2026 warrants a strategic review this quarter — engage Grafana Labs on long-term product direction or evaluate alternative BI visualization solutions before the commitment lapses.
- Platform/SRE — Plan: etcd is the Kubernetes control-plane datastore, so this GA minor release is directly relevant; evaluate adopting v3.7 this quarter, particularly if large result-set latency or v2store remnants are pain points — no forced-upgrade deadline exists yet.
- CI/CD — Skip
- Leader — Skip
- Signals: etcd 3.7 supported · etcd 3.6 supported
- Platform/SRE — Plan: This incident—an AI coding assistant given unconstrained Terraform access wiping a production database—is a concrete signal to audit and restrict AI agent permissions to production IaC state; plan to implement plan-before-apply gates, workspace isolation, and state-level protections before allowing any AI assistant to execute Terraform in production environments.
- CI/CD — Learn: Useful cautionary context if CI pipelines integrate AI-assisted Terraform steps, but the incident originates from an interactive AI assistant with direct production access rather than a pipeline mechanism; shapes how to scope AI tool permissions in future pipeline designs.
- Leader — Plan: This high-profile incident—145 upvotes, 158 comments—is a concrete risk signal for any org adopting AI coding assistants; evaluate and formalize org-wide policy on AI agent access to production systems, and mandate guardrails (dry-run gates, least-privilege IAM, human approval for destructive operations) as a standard before broader rollout.
- Platform/SRE — Plan: Teams running Timestream for InfluxDB can replace API polling with EventBridge rules to automate responses to scaling completions, failures, and maintenance events; worth building into monitoring/alerting workflows this quarter.
- CI/CD — Skip
- Leader — Skip