Platform Changelog

feedsince 2026-10-08patches hidden unless security or breaking

2026-10-292 days ago

Kubernetes MCP Serverv0.1.0minor++++++**Kubernetes MCP Server v0.1.0 added API-based filtering for Kiali, a multicluster evaluation suite for context tools, and tracking of in-flight MCP requests. It also added observability toolset tests, reading TOML config from stdin, and structured PipelineRun diagnosis. Fixes cover requiring Perses for show_timeseries and reporting metric LogQL queries instead of a JSON decode error.platform teamsPlatform teams running this MCP server get new Kiali filtering, PipelineRun diagnosis, and an in-flight request metric to watch. The stdin config option may simplify automated deployments.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

The New Stack: Why MCP servers should tell agents what to do nextpostAWS developer advocate James Ward argues that MCP servers should return guidance with data, telling the agent what it just did, what it might do next, and where to find more. He describes AWS adding a session ID parameter to tools so individual calls can be traced as one journey, with a second parameter carrying the user's goal for evaluation. Ward also said AWS ships a CLI and skills alongside MCP because MCP's OAuth model cannot switch between AWS profiles the way the CLI can.platform teamsPlatform teams exposing MCP servers can add session and goal parameters to tools and build evals that compare user intent with agent paths, then adjust tool descriptions or batch tools based on observed patterns. The article presents these as AWS practices rather than a released standard, so no protocol change is implied.The New Stack ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

InfoQ: Datadog Builds a Specialist AI Model for SRE InvestigationsannouncementDatadog has released Scout, a model trained with reinforcement learning to investigate production alerts inside its Bits Investigation AI SRE product. It is in closed preview with Datadog engineers and a small number of customers. Datadog says Scout matched larger models on its own AlertEval benchmark at a lower estimated inference cost, and resolved 71 to 80 of 90 faults on the public SREGym set depending on effort level.platform teamsPlatform and SRE teams evaluating AI incident investigation should note that the cost and benchmark figures come from Datadog's own tests and no prices are published, so independent results are needed. Scout only diagnoses and proposes recovery actions, and an engineer still makes any change.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-283 days ago

Amazon EKS Dashboard now provides fleet-wide visibility into certificate authority (CA) rotationannouncementAmazon EKS announced CA rotation visibility in the Amazon EKS Dashboard, which shows CA rotation status across clusters, clusters with CAs approaching expiration, and upcoming automated rotation events. The dashboard aggregates data across accounts and Regions through AWS Organizations, requires trusted access enabled in the management account, and is available at no additional cost. The source says CA rotation support extends to all commercial AWS Regions.platform teamsPlatform teams operating many EKS clusters can check CA rotation status and upcoming rotation events from one dashboard instead of per cluster. Enabling it requires trusted access for the dashboard in the organization's management account.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-274 days ago

The New Stack: The hidden failure paths that affect Kubernetes control plane availabilitypostThe article describes three control plane failure paths: an extension API server that published an invalid OpenAPI v2 schema after a dependency upgrade, which made Helm reject charts using only core resources; a DaemonSet rolling restart whose many agents rebuilt cluster-wide Pod informers at once, creating a request storm; and a deep liveness probe on a component in the API request path that restarted it repeatedly during a dependency outage. The author recommends testing the published OpenAPI documents, narrowing informer watch scopes, and reconsidering probe contracts. The source text is cut off before the KMS section finishes.platform teamsPlatform teams running aggregated API servers should fetch and validate /openapi/v2 and /openapi/v3 output after upgrades, since process health checks do not catch schema breakage. Teams running DaemonSet agents should narrow informer scopes and consider how recovery restarts synchronize list calls.The New Stack ↗Helmwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

CNCF: OpenTelemetry-powered distributed tracing and Kubernetes events in OpenChoreopostOpenChoreo, a CNCF Sandbox internal developer platform, uses the OpenTelemetry Collector to add distributed tracing to its observability plane. A local Collector in each data plane receives OTLP spans, enriches them with Kubernetes metadata via k8sattributes, applies tail sampling, and exports to a central Collector or cloud backend. The article also describes a custom Collector distribution with a k8seventenrich processor that persists Kubernetes events with OpenChoreo labels beyond the API server's default retention of about an hour.platform teamsPlatform teams running OpenChoreo or a similar IDP get traces and persisted, labeled Kubernetes events in the portal and through the observability MCP server. Teams building their own pipeline can reuse the pattern of pod-association enrichment for spans and informer-cache enrichment for events, which needs a custom processor because events do not map to pods.CNCF Blog ↗Kubernetes MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-265 days ago

Measuring developer experience on an Amazon EKS developer platformpostThe AWS Containers Blog post explains the DORA metrics (deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time) and how to collect them on an Amazon EKS developer platform. It walks through a demo setup that connects Argo Events, Argo Workflows, Argo CD, Argo Rollouts, Apache DevLake and Grafana. The post cites State of Platform Engineering Report Volume 4 and Enterprise Strategy Group figures on platform measurement and time to market.platform teamsPlatform teams on EKS can use the described Argo and DevLake pipeline to compute DORA metrics from existing deployment, rollout and pipeline events. The post's walkthrough is a demo, and the source text is cut off before the setup steps are complete.AWS Containers Blog ↗Amazon EKS Argo CD Argo Rollouts Argo Workflows DORA State of DevOps / AI-assisted development report Helmwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Tracing failures across Terraform state boundaries with AWS DevOps AgentpostAWS publishes a walkthrough of using AWS DevOps Agent to trace failures across separate Terraform state files. The sample has an infrastructure team tighten a security group egress rule, which breaks an application Lambda's DynamoDB access, and the agent correlates CloudWatch alarms and CloudTrail to point at the networking change. The post also covers provisioning the agent space with the hashicorp/awscc provider and bridging CloudWatch alarms to the agent's HMAC-signed webhook through a Lambda function. The source text is cut off before the walkthrough is complete.platform teamsPlatform teams that split infrastructure into multiple Terraform stacks could use an AI agent to trace cross-stack root causes, but the source shows only a demo. The webhook is console-only and not exposed as a Terraform resource, so it needs manual setup.AWS DevOps Blog ↗AWS DevOps Agent OpenTofuwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

The New Stack: The sandbox wasn’t enough: Why AI agent governance requires runtime observabilitypostThe article uses two incidents, an OpenAI cybersecurity evaluation that reached the public internet and an Anthropic review of 141,006 evaluation runs, to argue that a configured isolation boundary does not show what is reachable at runtime. It proposes four properties for runtime evidence: coverage, correlation, timeliness and auditability. It also describes how agent traces from Langfuse and infrastructure telemetry from ClickStack could share OpenTelemetry trace context.platform teamsPlatform teams running agents should instrument every trust boundary, including network egress, credential use and production writes, and link agent tool calls to infrastructure effects. They should also place synchronous policy gates in front of high-impact actions so a run can be suspended or its credentials revoked before effects become irreversible.The New Stack ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Troubleshooting Jenkins Performance: Kubernetes Edition - Part 2postThe CloudBees blog post describes steps for troubleshooting Jenkins performance issues in a Kubernetes setup where no production-ready APM tool is available. This is the second part of a series on the topic. The source text provided is only a short introduction, so the specific steps and findings are not described here.platform teamsPlatform teams running Jenkins on Kubernetes may find the troubleshooting approach useful when they lack APM tooling, but the source text does not specify concrete tools or changes.CloudBees Blog ↗CloudBees Jenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-247 days ago

The New Stack: Why Kubernetes autoscalers keep fighting each other (and why the solution must be autonomous)postThe article argues that Kubernetes autoscalers such as HPA, VPA, KEDA and Karpenter act on overlapping variables and can conflict, for example VPA shrinking requests that pushes HPA to scale out, or Argo CD reverting HPA replica changes. It describes four collision patterns and proposes a unified control layer that jointly decides replicas, resource requests and node capacity. The piece presents no new measured data beyond an illustrative example and a cited cluster CPU utilization figure of about 8%.platform teamsPlatform teams running HPA, VPA, KEDA or Karpenter together should check for overlapping writes to replicas and resource requests, and for GitOps auto-sync reverting autoscaler changes. The article offers no shipped tooling, so nothing changes in existing tools today.The New Stack ↗Karpenter Argo CD Flux Helmwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

The New Stack: Before you expand your GPU pool, measure the outcomepostThe article argues that teams running AI workloads on Kubernetes should define outcomes, deadlines, and costs before expanding a GPU pool. It suggests staggering batch jobs with scheduling flexibility, load-testing sustainable serving capacity, and joining OpenCost allocation data with verified outcome records to compute cost per verified outcome.platform teamsPlatform teams can use OpenCost allocation data joined with serving telemetry and outcome records to decide between scheduling changes, batching, resizing, model changes, or new GPUs. The article notes OpenCost proposal 3915 for serving-engine telemetry is still a draft.The New Stack ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-238 days ago

The New Stack: AI jobs are waiting while GPUs sit idle. Kubernetes has a new plan.postThe New Stack's Road to KubeCon column covers several Kubernetes topics: a HPE blog post on an open-source tool that gathers pod-restart diagnostics to Slack, an AWS post on scheduler and autoscaler friction for GPUs, and the llm-d v1.0 release. It also reports that in one benchmark by Skyhook's Radar, Claude Code given read-only MCP context diagnosed 50 injected faults faster than with shell and kubectl access, reaching a correct diagnosis within two minutes on 86% of faults versus 60%. Splunk's State of Observability 2026 survey of 2,050 professionals reports that over half cannot effectively measure AI quality or control AI costs.platform teamsPlatform teams evaluating AI troubleshooting agents may find that read-only MCP context improved speed in one author's benchmark, though the benchmark is a single small test by its author. The Splunk survey is vendor-commissioned, so its figures should be treated as indicative rather than verified.The New Stack ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-2110 days ago

K8sGPTv0.4.41patchsecurity+++**********!!!K8sGPT v0.4.41 was released with three dependency security updates, including containerd v1.7.36, spdystream v0.5.1 and otel sdk v1.45.0. It adds Claude 4.5 and 5.x model support for Amazon Bedrock, the ability to source customHeaders from the config file, and a prompt to auto-pull missing Ollama models. The release also fixes ten analyzer and completion issues, covering StatefulSet claim templates, NetworkPolicy selectors, Gateway API namespace filters, HTTPRoute namespace selectors, node-problem-detector conditions, and Kyverno ClusterPolicyReports.platform teamsPlatform teams running K8sGPT get fewer false or missed findings for NetworkPolicy, Gateway API and Kyverno reports after upgrading. The security items are dependency bumps rather than fixes in K8sGPT's own code.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Observability patterns for AI agents on Amazon EKSpostAWS Containers Blog describes two observability patterns for AI agents on Amazon EKS: a decentralized pattern where each agent exports traces straight to Langfuse, and a centralized pattern where traces pass through a shared OpenTelemetry Collector first. Both use the Strands Agents SDK for instrumentation, Bifrost as an LLM gateway routing to Amazon Bedrock, and OpenTelemetry GenAI conventions, with trace context propagated via traceparent headers. The post is cut off before its full results were shown in the source text.platform teamsPlatform teams choosing between the two patterns trade per-agent configuration sprawl against a shared Collector that must be sized and monitored as critical infrastructure. Adding a new telemetry backend is a Collector config change in the centralized pattern, and a change to every agent in the decentralized one.AWS Containers Blog ↗Amazon EKS Argo CD OpenTofuwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Amazon S3 server access log delivery to Amazon CloudWatch Logs now available in five additional AWS RegionsannouncementAmazon S3 server access log delivery to Amazon CloudWatch Logs is now available in the AWS GovCloud (US) Regions, the AWS European Sovereign Cloud, and the AWS China Regions. The source states the feature is now available in all AWS Regions. Delivery to CloudWatch Logs complements the existing delivery of server access logs to S3 general purpose buckets.platform teamsPlatform teams can query S3 access logs as they arrive in CloudWatch Logs, set alarms on error rates and traffic patterns, and encrypt the logs with AWS KMS keys. Amazon CloudWatch Logs vended log charges apply.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

CNCF: Distributed tracing for CI pipelines without touching a single workflow filepostThe post describes using the OpenTelemetry Collector's githubreceiver, behind a single org-level GitHub webhook, to turn workflow_run and workflow_job events into OTLP traces. A workflow becomes a parent span, with jobs and steps as nested child spans, so no workflow files need changing. The receiver is a contrib component at alpha stability, and the author advises pinning the collector version.platform teamsA platform team can get org-wide CI traces by pointing one org webhook at a collector, and new repos are covered automatically. The team must provide a publicly reachable endpoint, restrict it to GitHub's webhook ranges, have org admin access, and pin an alpha-stage collector version.CNCF Blog ↗GitHub Actions Actions Runner Controllerwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

CNCF: Before you evaluate an AI SRE, give your existing agent contextreportThe authors ran 50 Kubernetes faults from the SREGym benchmark on a live Amazon EKS cluster, comparing Claude Code with a shell and kubectl against Claude Code with read-only MCP tools from Radar, an open-source Kubernetes UI and MCP server the authors maintain. Both arms reached similar accuracy (46 vs 45 correct), but the context arm reached a correct diagnosis within two minutes on 86% of faults versus 60% with a shell, and used fewer tool calls on average (9.8 vs 16.3). The authors note that the context arm had different permissions from the shell arm, that each arm ran each fault once, and that they maintain the tool being tested.platform teamsPlatform teams evaluating AI SRE products can first measure whether their existing coding agent with read-only cluster context (current failures, change history, joined resources, filtered logs) diagnoses faults faster, using the published method and a read-only service account. Change history kept beyond Kubernetes event expiry and a read-only identity without Secrets or exec access are the concrete requirements the authors recommend checking.CNCF Blog ↗Kubernetes MCP Server Amazon EKS K8sGPTwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-2011 days ago

Amazon CloudWatch Alarms now supports tags in alarm actions payloadpostAmazon CloudWatch now lets customers include alarm tags in the payloads it sends to Amazon SNS, AWS Lambda, and Amazon EventBridge when an alarm changes state. The setting is off by default, can be configured per alarm, and supports all tags, selected tag keys, or all tags except selected keys. It applies to metric, composite, and log alarms and is unavailable in the Middle East (UAE) and Middle East (Bahrain) Regions.platform teamsPlatform teams routing many alarms through a shared notification pipeline can read owner, environment, or service tags directly from the event, removing per-event ListTagsForResource calls. Teams should check whether their Regions are covered and decide which tag keys to expose in messages.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1912 days ago

Amazon CloudWatch Omni is now available in additional AWS RegionsannouncementAWS says Amazon CloudWatch Omni, an AI-powered observability experience, is now available in eight more AWS Regions. The expansion adds Canada (Central), Asia Pacific (Mumbai, Singapore, Sydney, Tokyo), Europe (Frankfurt, London) and South America (São Paulo), on top of US East (N. Virginia), US West (Oregon) and Europe (Ireland). The source also describes spaces for cross-account telemetry, agent observability and an IDE extension, and says it works with Azure and GCP telemetry.platform teamsPlatform teams in the newly added Regions can now use Omni for cross-account and multi-cloud observability and AI-assisted root cause analysis. Teams should check pricing and data residency needs before adopting it, since the source only points to the pricing page.What's New with AWS ↗AWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

CNCF: How AI workloads are reshaping Kubernetes autoscalingpostThe article describes how Kubernetes autoscaling is being reworked for AI workloads, where the scheduler and the cluster autoscaler often disagree about what a usable node is. It covers Dynamic Resource Allocation for topology and device sharing, and notes that DRA support in autoscalers still varies by implementation. It also says workload-aware scheduling is beta and disabled by default, and that the autoscaler does not yet take part in gang scheduling, with a SIG-Autoscaling proposal under discussion.platform teamsPlatform teams running GPU node pools should check whether their autoscaler supports DRA claims and provisioning requests, since without that a pending pod may trigger an incompatible node launch or wasted capacity. Gang scheduling for large jobs still depends on a bolt-on provisioning request path that is best effort and provider dependent.CNCF Blog ↗Karpenter Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

InfoQ: Buildkite Adds Scoped Secrets and New Agentic CI ToolspostBuildkite has introduced pipeline-scoped secrets and new Model Context Protocol tools for validating pipelines, diagnosing failed builds and repairing webhooks. It also added Linux arm64 support to its GitHub Actions compatibility layer and expanded OpenTelemetry data in Buildkite Agent v4.1.0.platform teamsPlatform teams running Buildkite can scope secrets to individual pipelines and let MCP-connected agents validate pipelines and diagnose failures. Teams relying on the GitHub Actions compatibility layer on arm64 runners and on Buildkite Agent telemetry can now evaluate those changes.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1615 days ago

Amazon CloudWatch log centralization now available in AWS GovCloud and additional commercial RegionsannouncementAmazon CloudWatch log centralization is now available in AWS GovCloud (US) and 13 additional commercial Regions. The feature copies logs from multiple accounts and Regions into a single destination account, with rules scoped to an organization, organizational units, or selected accounts. Customers can centralize one copy of logs for free, and additional copies cost $0.05/GB.platform teamsPlatform teams running multi-account AWS estates in the newly covered Regions can aggregate logs into one account through AWS Organizations without building custom pipelines. Teams should check the per-GB charge for any second or further copy of logs.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1516 days ago

Launch AWS DevOps Agent to review findings and test results from AWS Resilience HubannouncementAWS Resilience Hub now integrates with AWS DevOps Agent. Users can launch a DevOps Agent investigation when they run a resilience test, which returns a structured analysis of symptoms, root cause, impact and observed recovery actions such as ARC Region switch. Users can also start an on-demand DevOps Agent task from a failure mode assessment finding to ask questions and build a mitigation plan.platform teamsPlatform and SRE teams using Resilience Hub on AWS can get agent-driven root cause analysis for resilience tests and help turning failure mode findings into mitigation plans. The source gives no details on permissions, audit or cost of the agent.What's New with AWS ↗AWS DevOps Agent Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1417 days ago

Amazon CloudWatch announces log routing and chained log parserspostAmazon CloudWatch pipelines now supports conditional log routing, which sends each event to a different CloudWatch log group based on conditions evaluated against processed fields. It also supports chained parsers, where later parser processors consume fields produced by earlier ones, such as parsing a JSON envelope and then applying a Grok parser. The capabilities are available in all commercial AWS Regions where CloudWatch pipelines is generally available and can be configured through the console, CLI, or SDKs.platform teamsPlatform teams can split mixed log streams into separate log groups and apply different retention and access controls per route within a single pipeline. Nested log formats can be parsed in sequence without a separate transformation stage.What's New with AWS ↗editorCorrection 2026-10-20: this was listed as a Amazon EKS release by mistake. It is What's New with AWS coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Why Is My Kubernetes Job Still Pending? Tracing Kueue Admission with HeadlamppostThe Kubernetes Blog published a walkthrough of using the 0.1.0-alpha Kueue plugin for Headlamp to trace why a Job stays suspended. The article steps through the Workload, LocalQueue, ClusterQueue, ResourceFlavor and Cohort views, and separates Kueue admission from Pod scheduling. The alpha plugin provides read-only views for Kueue v1beta2 resources.platform teamsPlatform teams running Kueue for batch or quota-managed workloads can use the Headlamp views to read Workload conditions and queue capacity without switching to kubectl for each step. The alpha plugin does not add create, edit, stop, resume or delete workflows.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1318 days ago

Amazon ECS adds LiveTaskCount and removes the charge for RunningTaskCount metricannouncementAmazon ECS added a LiveTaskCount service metric that reports tasks in ACTIVATING, RUNNING, and DEACTIVATING states, including tasks draining during scale-in. The metric is available at no charge and does not require CloudWatch Container Insights. The existing RunningTaskCount metric in Container Insights also no longer incurs a charge, effective October 1, 2026.platform teamsPlatform teams running ECS can use LiveTaskCount for autoscaling and capacity planning without paying for Container Insights, and can drop charges previously paid for RunningTaskCount. RunningTaskCount still only counts tasks whose current and desired state are both RUNNING, so it is not a substitute for LiveTaskCount in scale-in logic.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1219 days ago

InfoQ: Spotify More Than Doubled Monthly Code Changes as AI Accelerated Developmentcase studySpotify reports that AI-assisted development more than doubled its monthly merged changes. The company says it is reviewing quality and reliability controls across its engineering organization in response. Described changes include testing, observability, rollback capacity, workload prioritization and automated maintenance.platform teamsPlatform teams facing a similar rise in change volume can compare their testing, observability and rollback practices against the areas Spotify names. The source gives no specific tooling, metrics or figures beyond the merged-change increase.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1120 days ago

InfoQ: Foresight AI Brings Gremlin Agents to Reliability EngineeringpostGremlin has announced general availability of Foresight AI, an agentic product. According to the source, it analyzes services for potential failures, recommends changes, and reruns tests to check whether a fix works.platform teamsPlatform teams evaluating AI-driven reliability tooling can now consider Foresight AI as a GA option, but the source gives no details on integrations, pricing, or how it connects to existing pipelines or clusters.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1021 days ago

Karpenterv1.15.0minor++++++++++********Karpenter v1.15.0 adds node repair as a voluntary disruption method, including reboot as a node action, terminate-first repair for capacity-constrained NodePools, and a --legacy-node-repair flag to run the previous controller. It also adds metrics such as karpenter_pods_disrupted_total and labels on disruption metrics, plus AWS feature gates and CEL expressions for kubelet settings. The release notes list 41 additions and 35 fixes, with 189 maintenance lines omitted.platform teamsPlatform teams running Karpenter on EKS should review repair and disruption behavior, since node repair now runs as a voluntary disruption and default repair policies changed, and the --legacy-node-repair flag offers a fallback. The new disruption and reboot metrics give more detail for monitoring node churn.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

InfoQ: Cloudflare Traces Turns the Proxy Layer into OpenTelemetry Spans, with New Volume-Based PricingpostCloudflare put Traces into open beta, extending its automatic tracing from Workers to security rules, transformations, cache, routing and origin handling, emitted as OpenTelemetry spans. Traces accept and forward W3C traceparent headers, and Trace Rules allow targeted sampling. Pricing moves to ingestion and retention volume starting December 1.platform teamsPlatform teams that use Cloudflare in front of services can get proxy-layer spans in their existing OpenTelemetry backends, with sampling controls to limit volume. Teams should estimate ingestion and retention costs before December 1, since billing changes from the current model to volume-based.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

older entries

daily email

statuslast 30 days for lines

tools tracked43releases in registry964released in the last 30 days108entries published335breaking change lines18security lines84

change typestwo-column gutter, like git status

+addedNew functionality.
~changedExisting behavior changed.
-deprecatedStill works, scheduled for removal.
-removedDecommissioned, gone in this version.
*fixedA defect corrected.
!securityA vulnerability closed or a dependency patched for one.
!breakingFlag in the first column; the change needs action before upgrading.

filter

categoryall idp & portals ai agents on platform ci/cd observability supply chain cost & governance reports & dx data enterprise app platforms

showmajor only releases case studies postmortems include patches

Platform Changelog: what shipped in platform engineering, developer experience and DevOps