platformchangelog.dev
43 tools

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

feedbefore 2026-09-11all releases, patches included
newest entries
2026-09-101 month ago
Kubernetes v1.37: Scheduler Preemption for In-Place Pod Resize (Alpha)postKubernetes v1.37 adds an Alpha feature behind the InPlacePodVerticalScalingSchedulerPreemption feature gate that lets the kube-scheduler preempt lower-priority Pods on the same node so that a running Pod's deferred in-place resize can be actuated. Previously a Deferred resize could remain pending indefinitely until node capacity freed up. The Kubelet delegates this preemption decision to the scheduler rather than evicting locally.platform teamsPlatform teams bin-packing lower-priority batch workloads can allow higher-priority Pods to scale up in place without restarts, but must enable the gate across kube-apiserver, kube-scheduler and kubelet on v1.37 clusters. The feature is Alpha, and the new spec.podPreemptionPolicy node field lets controllers opt specific nodes out of resize preemption.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Amazon EKS v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Kubernetes v1.37: Introducing Node Lifecycle ConditionspostKubernetes v1.37 reserves five well-known Node condition types: DrainInProgress, Drained, MaintenancePlanned, MaintenanceInProgress, and GracefulNodeShutdownInProgress. It also adds an Alpha NodeLifecycleConditions feature gate, disabled by default, which the release describes as a no-op in v1.37 since no core component reads the conditions yet. Administrators or authorized controllers are responsible for setting and clearing them.platform teamsPlatform teams can start publishing these conditions today from drain and maintenance automation to give dashboards, alerts and tooling a common status signal. No core controller changes behavior based on them in this release, so scheduling and eviction still rely on existing mechanisms.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Amazon EKS v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-081 month ago
Kubernetes v1.37: Advancing Workload-Aware SchedulingpostKubernetes v1.37 graduates the core Workload and PodGroup APIs, which enable gang scheduling, to Beta, along with workload-aware preemption and shared DRA ResourceClaims for PodGroups. The release adds a CompositePodGroup API for multi-level hierarchical scheduling, and makes minCount mutable so controllers can resize gangs. The alpha v1alpha2 API was replaced by v1alpha3, and the disruptionMode values were renamed from PodGroup and Pod to all and single.platform teamsPlatform teams running batch or AI/ML workloads on Kubernetes should plan for the v1alpha2 to v1alpha3 breaking change and the disruptionMode rename if they use the alpha APIs. Teams can also begin evaluating native gang scheduling and hierarchical scheduling for JobSet and LeaderWorkerSet workloads.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Kubernetes v1.37: KubeletInUserNamespace (aka Rootless mode) Graduates to BetapostKubernetes v1.37 promotes the KubeletInUserNamespace feature gate to beta, allowing kubelet, container runtimes, CNI plugins and kube-proxy to run as a non-root user inside a Linux user namespace. The feature gate is now enabled by default, but nodes only run rootless if they are set up that way outside Kubernetes. Kubelet now reports a runningInUserNamespace property on nodes.platform teamsPlatform teams can run node components without host root to limit container-breakout impact, but some CNI and CSI drivers may break, so test them first. Administrators can use the new runningInUserNamespace node property to keep root-dependent workloads off rootless nodes.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Kubernetes MCP Server v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Investigate DMS migration issues with AWS DevOps AgentpostAWS published a guide on extending AWS DevOps Agent with a sample MCP server that provides read-only, DMS-specific tools and 46 runbooks for investigating database migration issues. The server is deployed on AWS Lambda behind an IAM-authenticated function URL and registered with a DevOps Agent Space. The post describes five investigation scenarios run against a test migration from RDS MySQL to Aurora PostgreSQL.platform teamsPlatform teams running DMS migrations can evaluate a read-only MCP pattern for giving an agent migration-specific context, with tools restricted to Describe, Get, List, Lookup and TestConnection calls. Timing claims in the post come from the authors' own test runs and are not benchmarked.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-031 month ago
Open Policy Agentv1.20.2patch
Automating the Experimentation Lifecycle with Kiro, AWS DevOps Agent, and LaunchDarklypostAWS describes a reference architecture where AWS DevOps Agent runs a scheduled custom agent that plans feature-flagged experiments, uses Kiro CLI in a custom MCP server to write code and open pull requests, and deploys through GitHub Actions and AWS Amplify. LaunchDarkly runs the experiments and Guarded Releases, which roll back flag state when error or latency guardrails are breached. The post says the architecture is a reference implementation and that a more turnkey version is planned.platform teamsA platform team evaluating agent-driven delivery would need to scope MCP tools, restrict repos, branches and allowed tools, and manage credentials and state outside the container. The post notes that the scoping lives in server code rather than prompts, and that MCP tool allowlists are recommended for production.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSGitHub ActionsKubernetes MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-021 month ago
Kubernetes v1.37: Scale Workloads to Zero with HorizontalPodAutoscalerpostKubernetes v1.37 moves horizontal autoscaling to zero replicas to Beta and enables it by default. An HPA using an object or external metric can now scale a workload to zero and bring it back when the metric changes, a capability that previously required an add-on or the Alpha feature gate. The blog notes that Services do not buffer requests, so request-driven workloads need a separate buffering layer.platform teamsPlatform teams can scale idle queue consumers and batch workers to zero to cut costs on expensive CPU or GPU Pods, but must accept cold-start latency and make sure the external metrics adapter is reliable. Before upgrading, control plane components must both have the feature enabled, and HPAs with minReplicas 0 need an object or external metric.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Amazon EKS v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Jenkins Security Advisory 2026-09-02incidentJenkins published a security advisory dated 2026-09-02 that lists affected components: Jenkins core, update-center2, and about 18 plugins including GitLab, LDAP, SAML, Microsoft Entra ID, Script Security, and Pipeline: Groovy Libraries. The source text lists only the affected components and does not describe the vulnerabilities, severity, or fixed versions.platform teamsPlatform teams running Jenkins controllers should check the advisory for fixed Jenkins core and plugin versions and review which installed plugins are affected. The source text does not give the fixed versions, so the advisory itself must be consulted before deciding on upgrades.Jenkins security advisories ↗Jenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Automate planned lifecycle upgrades with AWS DevOps Agent and KiropostAWS describes a pattern in which AWS Health Planned Lifecycle Events for Amazon EKS trigger EventBridge and a Lambda function that starts AWS DevOps Agent to investigate the upgrade and produce a CDK change spec. The spec is validated in a GitHub Actions workflow, then Kiro CLI in headless mode edits a single stack file and a pull request is opened for human review. The post also describes an automated failure path that investigates failed deployments and opens a fix pull request, with one retry attempt.platform teamsPlatform teams running EKS on AWS could adapt this event-driven pattern to handle managed service end-of-support deadlines, with human review kept at the pull request. The source is a vendor blog post with sample code and does not report measured results.AWS DevOps Blog ↗Amazon EKSAWS DevOps AgentGitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-012 months ago
Flaggerv1.45.0minor+++**
Kubernetes v1.37: etcd RangeStream Cuts Memory Use on Large List ReadspostThe Kubernetes blog says etcd RangeStream is graduating to beta in Kubernetes v1.37 and pairs with etcd v3.7. RangeStream is a streaming version of the etcd Range read that sends results in chunks sized by bytes, so the API server and etcd hold less memory when reading large collections such as Pods. The EtcdRangeStream feature gate is on by default in v1.37, and the API server falls back to paginated Range reads if etcd is older than v3.7.platform teamsPlatform teams running clusters with many or large objects should see lower and more predictable kube-apiserver and etcd memory use during watch cache initialization and direct list fallbacks, provided etcd is upgraded to v3.7 or later. Teams can confirm use via the listStream operation label on etcd request duration metrics, or disable the gate with --feature-gates=EtcdRangeStream=false.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-312 months ago
Fluxv2.9.5patch+++++~~~~~~~~~~
Kubernetes v1.37: Storage Version Migration Enabled by DefaultpostStorage Version Migration has reached General Availability in Kubernetes v1.37 and is enabled by default on all v1.37 clusters. The built-in StorageVersionMigration API (storagemigration.k8s.io/v1) and its control plane controller rewrite existing stored resources to the current storage version when a StorageVersionMigration object is created. Migration progress is reported through status conditions that can be checked with kubectl.platform teamsPlatform teams can replace manual kubectl get/replace scripts or the out-of-tree kube-storage-version-migrator for CRD version cleanup and encryption at rest key rotation. Teams should confirm the CRD storedVersions field is updated after a successful migration before removing older API versions.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Optimize EKS operations with agents: Reduce MTTR with AWS DevOps Agent and a Kubernetes OperatorpostAWS describes a Kubernetes Operator that watches EKS pods, collects logs, events, node-level data and manifests when a failure occurs, and sends that context to AWS DevOps Agent through a generic webhook. The post says the Operator stores evidence in S3 or CloudWatch Logs before pods are rescheduled or deleted. Setup requires an Agent Space, an IAM role with Pod Identity, and building the Operator image from source because no prebuilt image is provided.platform teamsPlatform teams running EKS can evaluate automated incident evidence capture and agent-driven investigation, but must set up IAM, Systems Manager registration on nodes, and build and host their own image. Node-level collection is unavailable on Fargate.AWS DevOps Blog ↗Amazon EKSAWS DevOps AgentK8sGPTwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
daily email

One short email each morning: what shipped, what breaks, and a link to each change. Unsubscribe in one click. Privacy.

statuslast 30 days for lines
tools tracked43releases in registry964released in the last 30 days104entries published336breaking change lines18security lines82
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
categoryallidp & portalsai agents on platformci/cdobservabilitysupply chaincost & governancereports & dx dataenterprise app platforms
showmajor onlyreleasescase studiespostmortemsinclude patches