# Deployment Strategies

Deployment strategies are processes for delivering software from one version to another, including in-place, blue/green, canary, linear, rolling, and all-at-once deployments.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Mitigating CVE-2026-114938 in self-managed OpenSearch deployments

DevFeed: [Mitigating CVE-2026-114938 in self-managed OpenSearch deployments](<https://devfeed.tech/articles/mitigating-cve-2026-114938-in-self-managed-opensearch-deployments-146663.md>)

Original publisher: [Read original article](<https://opensearch.org/blog/mitigating-cve-2026-114938-in-self-managed-opensearch-deployments/>)

Author: Craig Perkins

Published: 2026-11-20T18:44:42Z

Content type: tutorial

Language: en

Sources: [OpenSearch](<https://devfeed.tech/sources/opensearch.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [opensearch](<https://devfeed.tech/topics/opensearch.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [archive](<https://devfeed.tech/tags/archive.md>), [blog](<https://devfeed.tech/tags/blog.md>), [compose](<https://devfeed.tech/tags/compose.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [debian](<https://devfeed.tech/tags/debian.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [docker](<https://devfeed.tech/tags/docker.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [mitigation](<https://devfeed.tech/tags/mitigation.md>), [opensearch](<https://devfeed.tech/tags/opensearch.md>), [operators](<https://devfeed.tech/tags/operators.md>), [release](<https://devfeed.tech/tags/release.md>), [technical](<https://devfeed.tech/tags/technical.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

The temporary mitigation for CVE-2026-114938 is to add the JVM option `-XX:-UseBASE64Intrinsics` to every affected self-managed OpenSearch node, then restart nodes one at a time and verify the option is active. The advisory scope described is OpenJDK 17 or later on x64 systems whose CPUs support AVX-512 VBMI; OpenJDK 8 and 11 and ARM systems are excluded. The excerpt gives deployment-specific steps: preserve existing JVM options in Docker, use the Operator's `nodePools[].jvm` field for Kubernetes, or add a separate file under `jvm.options.d` for Linux packages and archives. Disabling the optimized Base64 intrinsic may affect some workload performance. This is temporary; upgrade to an OpenSearch release with a fixed JDK when available, and verify current vendor guidance and release status before production changes.

### Source excerpt

This post explains how self-managed OpenSearch operators can identify deployments affected by CVE-2026-114938, apply the vendor-provided JVM mitigation, and prepare to upgrade when an OpenSearch release with the fixed JDK is available. The post Mitigating CVE-2026-114938 in self-managed OpenSearch deployments appeared first on OpenSearch.

## ELevate updates: upgrades to x86\_64\_v2 and from the installation ISO

DevFeed: [ELevate updates: upgrades to x86\_64\_v2 and from the installation ISO](<https://devfeed.tech/articles/elevate-updates-upgrades-to-x86-64-v2-and-from-the-installation-iso-146934.md>)

Original publisher: [Read original article](<https://almalinux.org/blog/2026-11-20-elevate-updates/>)

Author: Yuriy Kohut ELevate Project Engineer

Published: 2026-11-20T00:00:00Z

Content type: release

Language: en

Sources: [AlmaLinux](<https://devfeed.tech/sources/blog-on-almalinux.md>)

Topics: [project release](<https://devfeed.tech/topics/project-release.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [x86](<https://devfeed.tech/topics/x86.md>)

Tags: [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [almalinux](<https://devfeed.tech/tags/almalinux.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [epel](<https://devfeed.tech/tags/epel.md>), [framework](<https://devfeed.tech/tags/framework.md>), [iso](<https://devfeed.tech/tags/iso.md>), [release](<https://devfeed.tech/tags/release.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>), [upstream](<https://devfeed.tech/tags/upstream.md>), [v2](<https://devfeed.tech/tags/v2.md>), [x86-64](<https://devfeed.tech/tags/x86-64.md>)

### AI overview

ELevate Stable adds upgrades from AlmaLinux OS 9 to AlmaLinux OS 10 x86_64_v2 and AlmaLinux OS Kitten 10 x86_64_v2, using dedicated data packages and a downloaded x86_64_v2 rootfs; EPEL is the currently supported third-party repository for these paths. For air-gapped upgrades, `leapp preupgrade` and `leapp upgrade` accept `--iso` with a local target OS DVD image, which also serves the reboot phase. This applies to AlmaLinux 8-to-9 and 9-to-10 paths, including Kitten 10 and x86_64_v2. The ISO replaces only the target OS package source: ELevate must already be installed, and CRB and third-party packages must be handled after upgrading. The release syncs with leapp-repository 0.25.0 and framework 0.21.0, and fixes include an LVM-on-MD-RAID emergency-shell issue, custom repositories for Foreman/Katello or private mirrors, and a Secure Boot check for CentOS 7 upgrades to a different vendor. The article recommends backups or snapshots and a sandbox trial.

### Source excerpt

Hello everyone! We are happy to share that a new release of ELevate, the AlmaLinux project for in-place upgrades between major versions of Enterprise Linux distributions, is now available in ELevate Stable. It brings the upgrade path to AlmaLinux OS 10 x86_64_v2, the ability to upgrade from the installation ISO on air-gapped systems, and a sync with the current upstream leapp-repository version 0.25.0. Upgrade to AlmaLinux 10 x86_64_v2 AlmaLinux OS 10 is built for the x86_64_v3 architecture level by default, and we also provide a parallel x86_64_v2 build for older hardware. Earlier this year we asked you to help us test the upgrade to that build in ELevate NG. Thank you to everyone who tried it and reported results!

## CVE-2026-123890: Critical Authentication Bypass in VMware vCenter

DevFeed: [CVE-2026-123890: Critical Authentication Bypass in VMware vCenter](<https://devfeed.tech/articles/cve-2026-123890-critical-authentication-bypass-in-vmware-vcenter-144830.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter>)

Author: Rapid7

Published: 2026-11-19T21:06:24Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [armory-castle](<https://devfeed.tech/tags/armory-castle.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123890](<https://devfeed.tech/tags/cve-2026-123890.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [in-the-wild-exploitation](<https://devfeed.tech/tags/in-the-wild-exploitation.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [mandiant](<https://devfeed.tech/tags/mandiant.md>), [mitigation](<https://devfeed.tech/tags/mitigation.md>), [network](<https://devfeed.tech/tags/network.md>), [patch](<https://devfeed.tech/tags/patch.md>), [security](<https://devfeed.tech/tags/security.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>), [server](<https://devfeed.tech/tags/server.md>), [threat](<https://devfeed.tech/tags/threat.md>), [vcenter](<https://devfeed.tech/tags/vcenter.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-vcenter](<https://devfeed.tech/tags/vmware-vcenter.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

CVE-2026-123890 is a critical, actively exploited authentication bypass in vCenter's VMware Directory Service. An attacker with network access can exploit it without credentials to gain Administrator access; Broadcom rates it CVSSv3 9.8, and Mandiant/Google Threat Intelligence reports ARMORY CASTLE exploitation as early as September 2026. Broadcom says systems below the fixed versions need this update even if they received the earlier, distinct CVE-2026-59309 fix. No workaround is listed, and Quick Patch cannot apply the fixes, so Broadcom calls for an emergency upgrade through the deployment's standard update mechanism. Updates temporarily make management interfaces unavailable, while running VM and container workloads continue. The 8.0 U3m and 9.0.2.0200 updates add a "Back-in-Time" restriction affecting upgrades to VMware Cloud Foundation 9.1.1; customers already upgrading are advised to consult Broadcom's FAQ and interoperability matrix.

### Source excerpt

Overview On November 19, 2026, Broadcom published VMware Security Advisory VMSA-2026-0009, addressing five vulnerabilities in VMware products. The most severe of these, CVE-2026-123890, is an authentication bypass using an alternate path or channel (CWE-288) in the VMware Directory Service component of vCenter. Broadcom assigned the vulnerability a critical CVSSv3 score of 9.8. A malicious actor with network access to an affected vCenter deployment may exploit CVE-2026-123890 without credentials to bypass authentication and gain unauthorized access to the system as the Administrator user. Mandiant privately reported the issue to Broadcom. Also, Mandiant/Google Threat Intelligence confirmed in-the-wild exploitation of CVE-2026-123890 by Chinese state-linked threat actor ARMORY CASTLE as early as September 2026. CVE-2026-123890 is distinct from the vCenter authentication bypass vulnerability CVE-2026-59309 that Broadcom addressed earlier in 2026. The vendor FAQ states that all vCenter systems below the versions fixed by VMSA-2026-0009 require the new update, including systems that already received the earlier fix. Broadcom characterizes the vCenter update as an emergency change requiring prompt action. Mitigation guidance Vendor-provided updates are available for CVE-2026-123890. Broadcom lists no workaround, and the patches cannot be applied using vCenter Quick Patch. Organizations should prioritize upgrading vCenter on an emergency basis, outside of normal patch cycles, using the standard update mechanism for their deployment. VMware Product Affected Version Fixed Version / Patch VMware Cloud Foundation / vSphere Foundation 9.1.x.x 9.1.1.0200 VMware Cloud Foundation / vSphere Foundation 9.0.x.x 9.0.2.0200 VMware vCenter Server 8.0 8.0 U3m VMware vCenter Server 7.0 Contact Broadcom Support (extended-support customers) VMware Cloud Foundation 5.x 5.2.5 VMware Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 8.0 U3m -- KB463116 VMware Telco Cloud Infrastructure 3.0 8.0

## How Amazon ECS handles blue/green, canary, and linear deployments

DevFeed: [How Amazon ECS handles blue/green, canary, and linear deployments](<https://devfeed.tech/articles/how-amazon-ecs-handles-blue-green-canary-and-linear-deployments-143800.md>)

Original publisher: [Read original article](<https://thenewstack.io/amazon-ecs-deployment-strategies/>)

Author: Simon Gao

Published: 2026-11-19T16:00:00Z

Content type: article

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [blue-green deployment](<https://devfeed.tech/topics/blue-green-deployment.md>), [canary release](<https://devfeed.tech/topics/canary-release.md>), [traffic splitting](<https://devfeed.tech/topics/traffic-splitting.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Argo Rollouts](<https://devfeed.tech/topics/argo-rollouts.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-ecs](<https://devfeed.tech/tags/amazon-ecs.md>), [aws-marketplace](<https://devfeed.tech/tags/aws-marketplace.md>), [canary](<https://devfeed.tech/tags/canary.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud-services](<https://devfeed.tech/tags/cloud-services.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [green](<https://devfeed.tech/tags/green.md>), [linear](<https://devfeed.tech/tags/linear.md>), [linear-deployments](<https://devfeed.tech/tags/linear-deployments.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [sponsor-aws-marketplace](<https://devfeed.tech/tags/sponsor-aws-marketplace.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>)

### AI overview

Amazon ECS includes progressive deployment controls in its service deployment configuration and API. Rolling deployments replace tasks in batches and remain a suitable default, but rollback requires another rollout, so a bad version may keep serving traffic while alarms process. Blue/green keeps the old tasks ready during a configurable bake period of up to 24 hours, allowing rollback by shifting traffic back; it can require double compute capacity during deployment. ECS also supports linear traffic shifts in equal increments and canary shifts in two steps. Rollback and monitoring options include task health circuit breakers, CloudWatch alarms, StopServiceDeployment, and lifecycle hooks. Hooks can use Lambda to poll external monitoring such as Datadog, Splunk, or Grafana; a pause hook can instead trigger an EventBridge process that resumes deployment with ContinueServiceDeployment. The excerpt says strategies can work without a load balancer or listed network integrations, while lifecycle hooks have limited stages for rolling deployments and production traffic shift requires Lambda.

### Source excerpt

Deploying containers safely at scale can mean assembling your own system: traffic-splitting logic, alarm evaluation, rollback automation, approval gates. It's The post How Amazon ECS handles blue/green, canary, and linear deployments appeared first on The New Stack.

## Bring charts, queries, and context into one shareable document: Introducing Grafana Notebooks

DevFeed: [Bring charts, queries, and context into one shareable document: Introducing Grafana Notebooks](<https://devfeed.tech/articles/bring-charts-queries-and-context-into-one-shareable-document-introducing-grafana-notebooks-145261.md>)

Original publisher: [Read original article](<https://grafana.com/blog/bring-charts-queries-and-context-into-one-shareable-document-introducing-grafana-notebooks/>)

Author: Daniel Moosdeen Mui

Published: 2026-11-19T15:22:49Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-work](<https://devfeed.tech/tags/ai-assisted-work.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [charts](<https://devfeed.tech/tags/charts.md>), [context](<https://devfeed.tech/tags/context.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [explore](<https://devfeed.tech/tags/explore.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-assistant](<https://devfeed.tech/tags/grafana-assistant.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [incident](<https://devfeed.tech/tags/incident.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [notebook](<https://devfeed.tech/tags/notebook.md>), [observability](<https://devfeed.tech/tags/observability.md>), [panel](<https://devfeed.tech/tags/panel.md>), [payment](<https://devfeed.tech/tags/payment.md>), [queries](<https://devfeed.tech/tags/queries.md>), [question](<https://devfeed.tech/tags/question.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>), [recommendation](<https://devfeed.tech/tags/recommendation.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [traces](<https://devfeed.tech/tags/traces.md>), [visualization](<https://devfeed.tech/tags/visualization.md>)

### AI overview

Grafana Notebooks provide a shareable working document for combining charts, Explore queries, Assistant visualizations, and written reasoning. Users can add a dashboard panel or Explore content to a new or existing notebook, refine the query without changing the source dashboard, set an absolute time range on a panel, and reorder blocks; edits save automatically. Assistant visualizations can be added from the side pane or Workspace, and the notebook's Assistant pane can help modify a visualization or refine the document. In the checkout example, evidence points to one provider's timeouts and a deployment change to its timeout setting; the notebook presents this as a suspected cause to test, not a confirmed conclusion. Teammates with access can inspect the analysis and queries, while testing occurs separately in the service's test environment. Notebooks are in public preview in Grafana Cloud and self-managed Grafana; self-managed setup requires enabling the `dashboard.notebooks` feature toggle. Cloud access is rolling out over the coming weeks. Comments and live editing are described as being explored.

### Source excerpt

A teammate asks why you think a deployment caused checkout failures. You have an error-rate chart in your dashboard, a query that narrows the failures to one payment provider, and an explanation you've been exploring with Grafana Assistant. To bring your teammate up to speed, you start collecting screenshots and query links, then write out how they connect. That explanation is part of the analysis. Your teammate needs to see what supports the conclusion and where you're still making an assumption. As findings come from both your own exploration in Grafana and from AI-assisted work, having one place to examine them together becomes key. Grafana Notebooks help you do just that, bringing charts, queries, and findings from Assistant together in one working document, so teammates can follow your reasoning and assess next steps. In this post, we'll use the checkout example above to show how this works in practice, then look at how Notebooks can support rollout decisions and post-incident reviews. How Notebooks work: develop your analysis in a working document Through conversations with users, we've heard a recurring need for a lightweight place to work through a question and share the results. Notebooks give that work room to develop inside Grafana, from an initial observation to a recommendation someone can assess. You can start with a panel you've already found. Select Add to notebook from its dashboard menu, or from the Add menu in Explore, and choose a new or existing notebook. Then add your explanation and reorder the blocks as the argument takes shape. Your edits save automatically. Assistant can contribute to your working document, too. Add a visualization generated in an Assistant conversation directly to a notebook, whether you're using the side pane or Workspace. Once you're in the notebook, open the Assistant side pane to ask for changes to a visualization or help refining the document. You can also edit the content directly as your analysis develops. Work thro

## Keeping your databases up to date: From upstream release to you

DevFeed: [Keeping your databases up to date: From upstream release to you](<https://devfeed.tech/articles/keeping-your-databases-up-to-date-from-upstream-release-to-you-144299.md>)

Original publisher: [Read original article](<https://blog.ovhcloud.com/en/posts/managed-database-image-updates/>)

Author: Elena Luoto

Published: 2026-11-19T06:00:00Z

Content type: article

Language: en

Sources: [OVHcloud Blog](<https://devfeed.tech/sources/ovhcloud-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [staging](<https://devfeed.tech/topics/staging.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [builds](<https://devfeed.tech/topics/builds.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [version](<https://devfeed.tech/topics/version.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [api](<https://devfeed.tech/tags/api.md>), [apt](<https://devfeed.tech/tags/apt.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [automation](<https://devfeed.tech/tags/automation.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [builds](<https://devfeed.tech/tags/builds.md>), [databases](<https://devfeed.tech/tags/databases.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [image](<https://devfeed.tech/tags/image.md>), [pre-production](<https://devfeed.tech/tags/pre-production.md>), [production](<https://devfeed.tech/tags/production.md>), [release](<https://devfeed.tech/tags/release.md>), [sign-off](<https://devfeed.tech/tags/sign-off.md>), [tests](<https://devfeed.tech/tags/tests.md>), [upstream](<https://devfeed.tech/tags/upstream.md>), [upstream-release](<https://devfeed.tech/tags/upstream-release.md>), [version](<https://devfeed.tech/tags/version.md>), [weekly](<https://devfeed.tech/tags/weekly.md>)

### AI overview

Emile checks 15 engine/version pairs weekly and skips rebuilding when the current production tag matches the newest upstream package; for Valkey, it checks GitHub, and accepts a version only once release notes appear. When a rebuild is needed, it starts from clean Debian using shared Packer and Ansible recipes. New images go to a snapshot registry and must pass pre-production checks, including upgrades from current and earlier major versions. A team member manually approves promotion from the master branch; afterward, 5% of the production fleet moves to the image daily in randomized customer order. Builds also fail when vendor defaults have changed, prompting human review. If no version is new, a manual rebuild remains available for base-image fixes and follows the same tests and approval gate.

### Source excerpt

Learn how we keep databases up to date: a weekly version check, clean image builds, pre-production tests, and a human sign-off before release.

## Amazon RDS for MySQL LTS version 9.7 is now generally available

DevFeed: [Amazon RDS for MySQL LTS version 9.7 is now generally available](<https://devfeed.tech/articles/amazon-rds-for-mysql-lts-version-9-7-is-now-generally-available-141384.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/amazon-rds-for-mysql-lts-version-9-7-is-now-generally-available/>)

Author: Sabalesh Mahajan

Published: 2026-11-18T20:52:19Z

Content type: release

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [MySQL](<https://devfeed.tech/topics/mysql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [mysql group replication](<https://devfeed.tech/topics/mysql-group-replication.md>)

Tags: [active-active](<https://devfeed.tech/tags/active-active.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-relational-database-service](<https://devfeed.tech/tags/amazon-relational-database-service.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-database-migration-service](<https://devfeed.tech/tags/aws-database-migration-service.md>), [blue-green-deployment](<https://devfeed.tech/tags/blue-green-deployment.md>), [buffer-pool](<https://devfeed.tech/tags/buffer-pool.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [cdc-tools](<https://devfeed.tech/tags/cdc-tools.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [checklist](<https://devfeed.tech/tags/checklist.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [lts](<https://devfeed.tech/tags/lts.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-mysql](<https://devfeed.tech/tags/rds-for-mysql.md>)

### AI overview

Amazon RDS for MySQL 9.7 is generally available as the community's latest LTS version. Upgrade from 8.4 directly to 9.7; MySQL 8.0 must first move to 8.4, and 5.7 requires staged upgrades through 8.0 and 8.4. The post recommends Blue/Green deployments to test compatibility before promotion. Before upgrading, address key changes: `rdsproxyadmin` is reserved; `mysql_native_password`, `MD5()` and `SHA1()` are unavailable; TLS is required by default; password validation moves to renamed component settings; and `EXPLAIN` defaults to TREE format. RDS 9.7 uses `gtid_mode=ON_PERMISSIVE`, so outbound replicas must be at least `OFF_PERMISSIVE`. Multi-AZ DB clusters with two readable standbys are unsupported at launch. New capabilities include opt-in Hypergraph optimization, JSON Duality Views and Group Replication components for metrics, flow control, member recovery and primary election.

### Source excerpt

Amazon RDS for MySQL now supports MySQL 9.7, the latest community LTS version, alongside 8.0 and 8.4. This post covers what's new in 9.7, the key breaking changes, and how to upgrade safely from MySQL 8.4 using Amazon RDS Blue/Green deployments.

## How AT&T Turns Signed Evidence into Deployment Decisions with Kyverno

DevFeed: [How AT&T Turns Signed Evidence into Deployment Decisions with Kyverno](<https://devfeed.tech/articles/how-at-t-turns-signed-evidence-into-deployment-decisions-with-kyverno-139209.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/18/how-att-turns-signed-evidence-into-deployment-decisions-with-kyverno/>)

Author: Sagar Kundral

Published: 2026-11-18T01:14:41.413057Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [audit](<https://devfeed.tech/topics/audit.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [at-t](<https://devfeed.tech/tags/at-t.md>), [attestations](<https://devfeed.tech/tags/attestations.md>), [cel](<https://devfeed.tech/tags/cel.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [image-verification](<https://devfeed.tech/tags/image-verification.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>), [policy-as-code](<https://devfeed.tech/tags/policy-as-code.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [rules](<https://devfeed.tech/tags/rules.md>), [sbom](<https://devfeed.tech/tags/sbom.md>), [sigstore](<https://devfeed.tech/tags/sigstore.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

AT&T uses Kyverno ImageValidatingPolicy rules in CEL to turn verified image attestations into environment-specific admission decisions: a signed image can pass in development and fail in production if it lacks required evidence. The policy verifies signatures before reading claims, checks who built the image, then applies destination requirements; promotion checks do not replace admission because requests, policies and time-sensitive evidence can differ. AT&T uses one engine for internal and approved upstream or vendor images, with explicit trust roots; support for GitHub's private Sigstore root arrived in Kyverno 1.19, and the talk recommends 1.19.2 or later for Enforce mode. A single-laptop benchmark showed fewer registry calls and lower latency in newer versions, but these are not production figures and should be measured with local policies and registries. The talk also recommends planning failure behavior and narrow, expiring exceptions; retaining per-request decision evidence; and rolling out through audit, remediation, tiered enforcement and gradual expansion.

### Source excerpt

AT&T verifies signed provenance and SBOM attestations with a Kyverno ImageValidatingPolicy in CEL, then applies each environment's rules at admission.

## Enterprise Deployment of Governed Agents on Windows

DevFeed: [Enterprise Deployment of Governed Agents on Windows](<https://devfeed.tech/articles/enterprise-deployment-of-governed-agents-on-windows-139380.md>)

Original publisher: [Read original article](<https://blogs.windows.com/windowsdeveloper/2026/11/17/enterprise-deployment-of-governed-agents-on-windows/>)

Author: cstewart

Published: 2026-11-17T18:15:01Z

Content type: article

Language: en

Sources: [Windows Developer](<https://devfeed.tech/sources/windows-developer-blog.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [actions](<https://devfeed.tech/tags/actions.md>), [activity-report](<https://devfeed.tech/tags/activity-report.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-365](<https://devfeed.tech/tags/agent-365.md>), [agent-adoption](<https://devfeed.tech/tags/agent-adoption.md>), [agent-containment](<https://devfeed.tech/tags/agent-containment.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer](<https://devfeed.tech/tags/developer.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-deployment](<https://devfeed.tech/tags/enterprise-deployment.md>), [execution](<https://devfeed.tech/tags/execution.md>), [pc](<https://devfeed.tech/tags/pc.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [risk](<https://devfeed.tech/tags/risk.md>), [windows](<https://devfeed.tech/tags/windows.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The article presents enterprise agent deployment on Windows as a coordinated set of identity, execution containment, and management controls. Microsoft Entra Agent ID distinguishes agent activity; Microsoft Execution Containers (MXC) constrain local agent access to files, tools, and network resources, with isolation strength matched to workload risk. Intune or other MDM distributes policy, while Defender provides agent discovery and runtime protection, and Purview applies data loss prevention to supported interactions. The recommended rollout is to inventory workloads and prerequisites, observe real activity before enforcing policy, derive least-privilege rules, validate through deployment rings, and keep tested opt-out and rollback paths. The text notes that activity evidence has limited policy mappings and may omit some failures; capabilities vary by agent and scenario. It also describes Defender Audit-to-Block and staged Purview policy validation.

### Source excerpt

As AI agents become more capable, they promise substantial productivity gains across enterprise workflows. At the same time, they can collapse familiar execution boundaries and introduce new risk paths--from agent to human, agent to agent, agent to The post Enterprise Deployment of Governed Agents on Windows appeared first on Windows Developer Blog.

## Pull-request-only preset now available for preview builds

DevFeed: [Pull-request-only preset now available for preview builds](<https://devfeed.tech/articles/pull-request-only-preset-now-available-for-preview-builds-138552.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/pull-request-only-preset-now-available-for-preview-builds>)

Author: Mehul Kar

Published: 2026-11-17T02:37:03Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Netlify](<https://devfeed.tech/topics/netlify.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [builds](<https://devfeed.tech/tags/builds.md>), [preview](<https://devfeed.tech/tags/preview.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>)

### AI overview

The Ignored Build Step preset skips preview builds for branches without an open pull request while continuing production deployments and previews for branches with open pull requests. On GitHub and GitLab, skipped previews are canceled before they consume Build CPU Minutes. Enable it under Deployments > Configuration: in Ignored Build Step, choose "Only build previews for pull requests" from Behavior, then save.

### Source excerpt

A new Ignored Build Step preset lets you skip preview builds for branches without an open pull request. Production deployments and previews for branches with open pull requests continue to build. On GitHub and GitLab projects, skipped preview deployments are canceled before consuming any Build CPU Minutes. To enable this, open your project's Deployments > Configuration. Under Ignored Build Step, select Only build previews for pull requests from the Behavior menu and click Save. Learn more in the Ignored Build Step documentation. Read more

## November 2026 product update for Bitwarden Business plans

DevFeed: [November 2026 product update for Bitwarden Business plans](<https://devfeed.tech/articles/november-2026-product-update-for-bitwarden-business-plans-144655.md>)

Original publisher: [Read original article](<https://bitwarden.com/blog/november-2026-product-update-for-bitwarden-business-plans/>)

Published: 2026-11-17T00:00:00Z

Content type: release

Language: en

Sources: [The Bitwarden Blog](<https://devfeed.tech/sources/the-bitwarden-blog.md>)

Topics: [Release notes](<https://devfeed.tech/topics/release-notes.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [human centric design](<https://devfeed.tech/topics/human-centric-design.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [synchronization](<https://devfeed.tech/topics/synchronization.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [activation](<https://devfeed.tech/tags/activation.md>), [admin](<https://devfeed.tech/tags/admin.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [agencies](<https://devfeed.tech/tags/agencies.md>), [all](<https://devfeed.tech/tags/all.md>), [bitwarden](<https://devfeed.tech/tags/bitwarden.md>), [business](<https://devfeed.tech/tags/business.md>), [email](<https://devfeed.tech/tags/email.md>), [features](<https://devfeed.tech/tags/features.md>), [learn](<https://devfeed.tech/tags/learn.md>), [more](<https://devfeed.tech/tags/more.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [product](<https://devfeed.tech/tags/product.md>), [product-update](<https://devfeed.tech/tags/product-update.md>), [this](<https://devfeed.tech/tags/this.md>), [update](<https://devfeed.tech/tags/update.md>), [was](<https://devfeed.tech/tags/was.md>)

### AI overview

The November 2026 update adds manual invitations for SCIM- or Directory Connector-staged users, secure item sharing by link with non-Bitwarden recipients, and passkey support across Bitwarden apps and operating systems. Shared links use end-to-end encryption, recipient email verification, and controls such as timed deletion and view limits; an enterprise policy can disable sharing. Windows passkey integration requires the Microsoft Store desktop app. Apps on the same computer now share lock and unlock states, but users still sign in to each app separately. A redesigned interface will roll out automatically to cloud customers over several weeks starting November 19; self-hosted customers receive it in a future release. Existing API fields using "collections" continue to work, and admins should update internal documentation as terminology changes to "Shared folders" and "Shared vault." The update also urges immediate patching of self-hosted instances for disclosed nginx vulnerabilities.

### Source excerpt

Learn more about the features recently released in Bitwarden! This update was shared via email to all business admins and owners in November 2026.

## Introducing enhanced snapshots for Amazon Managed Service for Apache Flink

DevFeed: [Introducing enhanced snapshots for Amazon Managed Service for Apache Flink](<https://devfeed.tech/articles/introducing-enhanced-snapshots-for-amazon-managed-service-for-apache-flink-136180.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/introducing-enhanced-snapshots-for-amazon-managed-service-for-apache-flink/>)

Author: Francisco Morillo

Published: 2026-11-16T18:17:18Z

Content type: release

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Apache Flink](<https://devfeed.tech/topics/apache-flink.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-managed-service-for-apache-flink](<https://devfeed.tech/tags/amazon-managed-service-for-apache-flink.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [apache-flink](<https://devfeed.tech/tags/apache-flink.md>), [blue-green-deployment](<https://devfeed.tech/tags/blue-green-deployment.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [snapshots](<https://devfeed.tech/tags/snapshots.md>)

### AI overview

Enhanced snapshots are standalone AWS resources that let Amazon Managed Service for Apache Flink applications reuse state: start another application from a snapshot, export it to S3, or import a Flink savepoint. The text describes blue/green deployments, second-Region recovery, and migration from self-managed Flink. Blue/green cutover requires accounting for overlapping output and possible duplicates; both applications incur compute while running. Cross-Region recovery uses scheduled exports and S3 replication, trading more frequent exports for lower recovery work and higher operation, storage, and replication costs. Migration and restore require compatible Flink versions and matching operator UIDs; restores also require compatible state types and maxParallelism, and imported savepoints have validation prerequisites. Enhanced snapshots require Flink 1.20 or later, have separate IAM permissions, and persist until deleted, accruing storage charges. The text says snapshot storage is priced like application snapshots, with no added export/import charge; S3 charges still apply.

### Source excerpt

Enhanced snapshots for Amazon Managed Service for Apache Flink are now generally available. An enhanced snapshot is an AWS resource with its own ARN, decoupled from the application that created it, so you can start another application from it, export it to Amazon S3, and import savepoints for blue/green deployments, disaster recovery, and migrations.

## Every AKS Node You Can Patch in Place Is a Node That Can Drift

DevFeed: [Every AKS Node You Can Patch in Place Is a Node That Can Drift](<https://devfeed.tech/articles/every-aks-node-you-can-patch-in-place-is-a-node-that-can-drift-136236.md>)

Original publisher: [Read original article](<https://blog.devops.dev/aks-node-drift-azure-container-linux-immutable-os-90df033e23ac?source=rss----33f8b2d9a328---4>)

Author: Dave R | Microsoft Azure & AI MVP ☁

Published: 2026-11-16T13:25:26Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [aks](<https://devfeed.tech/tags/aks.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [commands](<https://devfeed.tech/tags/commands.md>), [container](<https://devfeed.tech/tags/container.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [devops](<https://devfeed.tech/tags/devops.md>), [guard](<https://devfeed.tech/tags/guard.md>), [image](<https://devfeed.tech/tags/image.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [layer](<https://devfeed.tech/tags/layer.md>), [linux](<https://devfeed.tech/tags/linux.md>), [node](<https://devfeed.tech/tags/node.md>), [nodepool](<https://devfeed.tech/tags/nodepool.md>), [os](<https://devfeed.tech/tags/os.md>), [patches](<https://devfeed.tech/tags/patches.md>), [patching](<https://devfeed.tech/tags/patching.md>), [pool](<https://devfeed.tech/tags/pool.md>), [secure-boot](<https://devfeed.tech/tags/secure-boot.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>), [update](<https://devfeed.tech/tags/update.md>), [weekly](<https://devfeed.tech/tags/weekly.md>)

### AI overview

Azure Container Linux (ACL) replaces patchable AKS node operating systems with signed, read-only images, reducing the risk of nodes drifting apart; nodes are replaced weekly instead of patched in place. The excerpt says ACL is generally available from Kubernetes 1.34 and is the documented destination for Azure Linux with OS Guard, whose patches end December 10, 2026. Existing Ubuntu or Azure Linux pools can be moved in place with Azure CLI 2.86.0 or later; AKS reimages the pool onto ACL. The excerpt does not provide the promised verification steps or operational limitations.

### Source excerpt

How Azure Container Linux locks down the node OS layer by layer, and how to move off OS Guard before its patches end December 10 Continue reading on DevOps.dev "

## Debug Kubernetes Deployment Failures with AI

DevFeed: [Debug Kubernetes Deployment Failures with AI](<https://devfeed.tech/articles/debug-kubernetes-deployment-failures-with-ai-136343.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/debug-kubernetes-deployment-failures-with-ai>)

Author: Animesh Pathak

Published: 2026-11-16T09:58:00Z

Content type: tutorial

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-debugging](<https://devfeed.tech/tags/ai-assisted-debugging.md>), [ai-chat](<https://devfeed.tech/tags/ai-chat.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [database](<https://devfeed.tech/tags/database.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [diagnosis](<https://devfeed.tech/tags/diagnosis.md>), [errors](<https://devfeed.tech/tags/errors.md>), [failures](<https://devfeed.tech/tags/failures.md>), [harness-ai-posts](<https://devfeed.tech/tags/harness-ai-posts.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

A stalled Kubernetes rollout initially showed only that progress had stopped. In a six exchange session, Harness AI Chat helped resolve five pipeline configuration problems and then directed the author to inspect the pods. Their crash looping app containers could not resolve the Postgres host; restoring Postgres made them ready, but the empty database then caused missing inventory table errors. Applying the repository's Liquibase changelog resolved those errors. The final pipeline added a preflight check for a ready database endpoint and a verification step for missing tables, catching these failures earlier. The author notes that the app's health endpoint checked database connectivity but not required tables, and that the example is a simplified blue green deployment intended for an isolated local cluster and dedicated test database.

### Source excerpt

Follow a Kubernetes deployment failure from initial diagnosis to root cause, uncovering pipeline issues, missing database dependencies, and schema errors. | Blog

## Single-second static deployments now support more assets

DevFeed: [Single-second static deployments now support more assets](<https://devfeed.tech/articles/single-second-static-deployments-now-support-more-assets-138553.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/single-second-static-deployments-now-support-more-assets>)

Author: Melkey Moksyakov

Published: 2026-11-16T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [CSS](<https://devfeed.tech/topics/css.md>), [web graphics](<https://devfeed.tech/topics/web-graphics.md>)

Tags: [assets](<https://devfeed.tech/tags/assets.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [css](<https://devfeed.tech/tags/css.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [fonts](<https://devfeed.tech/tags/fonts.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jpeg](<https://devfeed.tech/tags/jpeg.md>), [json](<https://devfeed.tech/tags/json.md>), [limits](<https://devfeed.tech/tags/limits.md>), [package-json](<https://devfeed.tech/tags/package-json.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [static](<https://devfeed.tech/tags/static.md>), [svg](<https://devfeed.tech/tags/svg.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel instant deployments can publish eligible static sites in about a second without a build step, now including CSS, images, fonts, and other listed assets alongside HTML and Markdown. Deploy via the CLI or REST API; Vercel detects eligibility automatically. Limits are 100 files and 25 MB total. Deployments exceeding those limits, containing JavaScript or other unsupported files, triggered by Git, or using a framework preset, custom build settings, a root-level package.json or Vercel configuration file, or a public/ directory still build as before. The update is rolling out across all plans.

### Source excerpt

Instant deployments let you deploy eligible static sites to Vercel in about a second, without a build step. They now support CSS, images, fonts, and other assets alongside HTML and Markdown. Deploy a landing page with its stylesheet and images, or a report created by your coding agent, through the Vercel CLI or REST API. With the CLI, run: Newly supported file types include: Styles and data: CSS, JSON, XML, plain text, and web manifests Images: SVG, PNG, JPEG, GIF, WebP, AVIF, and ICO Fonts: WOFF, WOFF2, TTF, OTF, and EOT Documents and media: PDF, MP4, WebM, MP3, WAV, and OGG Instant deployments support up to 100 files totaling 25 MB or less. Vercel detects eligible deployments automatically, with no configuration required. Deployments that exceed these limits, include JavaScript or other unsupported files, or are triggered by Git still build as before. The same applies to projects with a framework preset, custom build settings, a root-level package.json or Vercel configuration file such as vercel.json, or a public/ directory. This update is rolling out across all plans. Learn more in the deployment documentation. Read more

## Introducing Red Hat OpenShift Service Mesh 3.5

DevFeed: [Introducing Red Hat OpenShift Service Mesh 3.5](<https://devfeed.tech/articles/introducing-red-hat-openshift-service-mesh-3-5-135990.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/introducing-red-hat-openshift-service-mesh-35>)

Author: Jamie Longmuir

Published: 2026-11-16T00:00:00Z

Content type: release

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [istio](<https://devfeed.tech/topics/istio.md>), [SPIRE](<https://devfeed.tech/topics/spire.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-chatbot](<https://devfeed.tech/tags/ai-chatbot.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [ambient](<https://devfeed.tech/tags/ambient.md>), [dual-stack](<https://devfeed.tech/tags/dual-stack.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kiali](<https://devfeed.tech/tags/kiali.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [multicluster](<https://devfeed.tech/tags/multicluster.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [spire](<https://devfeed.tech/tags/spire.md>), [workload-identity](<https://devfeed.tech/tags/workload-identity.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

OpenShift Service Mesh 3.5 is generally available on OpenShift Container Platform 4.20 and later, including OpenShift 5.0. Based on Istio 1.31 and Kiali 2.33, it makes ambient-mode multiprimary multicluster and dual-stack IPv4/IPv6 generally available, and adds generally available SPIRE workload identity integration in sidecar mode, including federation; SPIRE is not yet supported in ambient mode. Sidecar-mode users can skip one Service Mesh minor release with revision-based upgrades, allowing workloads to jump two Service Mesh minor releases with one restart. Highlights include inherited mesh-wide resilience defaults, zone-aware load balancing, secure metrics scraping, and dynamic DNS for external HTTP destinations. Canary waypoint upgrades and standalone VM integration are Technology Preview; fleet management through Advanced Cluster Management is Developer Preview. Ambient multicluster currently supports multiprimary, multinetwork topology, while other topologies remain unsupported.

### Source excerpt

Red Hat OpenShift Service Mesh 3.5 is now generally available with Red Hat OpenShift Container Platform. Based on the Istio, Envoy, and Kiali projects, this release updates the version of Istio to 1.31 and Kiali to 2.33, and is supported on OpenShift Container Platform 4.20 and above, including Red Hat OpenShift 5.0. This release graduates multicluster with ambient mode, dual-stack IPv4/IPv6 with ambient mode, and Red Hat's zero trust workload identity manager (SPIRE) with sidecar mode to general availability, along with a substantial set of enhancements from Istio 1.31. Red Hat OpenShift 5.0

## Lights-out for AI coding agents: Gemini, ADK and a canary that rolls itself back

DevFeed: [Lights-out for AI coding agents: Gemini, ADK and a canary that rolls itself back](<https://devfeed.tech/articles/lights-out-for-ai-coding-agents-gemini-adk-and-a-canary-that-rolls-itself-back-131170.md>)

Original publisher: [Read original article](<https://medium.com/google-developer-experts/lights-out-ai-coding-agents-gemini-adk-canary-rollback-36ac910de522?source=rss----a67bd6fa7d58---4>)

Author: Nicola Guglielmi

Published: 2026-11-12T15:44:05Z

Content type: article

Language: en

Sources: [Google Developer Experts](<https://devfeed.tech/sources/google-developer-experts-medium.md>)

Topics: [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [google-adk](<https://devfeed.tech/topics/google-adk.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [canary release](<https://devfeed.tech/topics/canary-release.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [adk](<https://devfeed.tech/tags/adk.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [canary](<https://devfeed.tech/tags/canary.md>), [devops](<https://devfeed.tech/tags/devops.md>), [error](<https://devfeed.tech/tags/error.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [google-cloud-platform](<https://devfeed.tech/tags/google-cloud-platform.md>), [mutation](<https://devfeed.tech/tags/mutation.md>), [production](<https://devfeed.tech/tags/production.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

Lights-out moves a ticket from code changes to a staged canary using six agent roles, with scripts--not models--making GO/NO-GO decisions from numeric gates. PR checks include risk, secrets, dependencies, static analysis, tests, and mutation testing; post-merge, a signed image is deployed to 5% then 25% of traffic, with PromQL comparisons triggering automatic rollback. A person must approve promotion beyond 25%. It runs locally with Podman and recorded model responses, or live with a Gemini API key; its gates and deployment path remain active in either mode. Coding roles use Gemini CLI by default, while document roles use ADK with evals; Claude and OpenAI options are described, and a Claude change was blocked by the mutation threshold. The Google Cloud profiles are documented but untested, and the project says its approach is not yet proven on repositories outside its own.

### Source excerpt

What I learned putting six agents behind numeric gates, on a laptop, with no cloud account An agent opens a pull request on a codebase nobody on the team trusts. The tests are green. Now what? Do you merge it? Do you read every line? Do you let it reach production, and if so, who notices when it breaks? A lights-out factory runs in the dark because its safety systems are trusted. I wanted to know what that safety system looks like for AI coding agents that write and ship code, so I built one: lights-out. It takes a ticket all the way to production with six agent roles, and stops it at every point where a number says no. One human decision is left, before 100% of the traffic. Everything else is either a gate or a rollback. Reading every line doesn't scale when an agent can write a thousand of them before lunch. So I stopped trying to check the code and started designing the road it drives on: which files a ticket may touch, which numbers a change has to beat, how much real traffic a canary gets before a person looks at it. The agents pick the route, the guardrails decide where it can end up. My job moved from reviewing lines to choosing thresholds, and writing down where each one comes from. It runs complete on a laptop: no cloud account, no API key, no credit card. That constraint shaped most of the design, so I'll come back to it. The rule that comes first The model never decides whether a change is good. A number does. Every station in the pipeline is a script that prints exactly one line on stdout: GO: <name> or NO-GO: <name> -- <reason>. Tests, dependency advisories, static analysis, mutation score, the canary's error rate against stable. The agents write code, review it, explain a release and triage an alert. They never sit where a threshold sits. Written down it sounds obvious. In practice it's the first thing that erodes, because asking a model "is this canary healthy?" is easier than writing the PromQL query. So it became a rule with a check behind it, and ev

## LinkedIn Replaces Argo CD with a Custom GitOps Engine for Kubernetes Deployments

DevFeed: [LinkedIn Replaces Argo CD with a Custom GitOps Engine for Kubernetes Deployments](<https://devfeed.tech/articles/linkedin-replaces-argo-cd-with-a-custom-gitops-engine-for-kubernetes-deployments-130046.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/kubernetes-argocd-linkedin/>)

Author: Claudio Masolo

Published: 2026-11-12T09:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [GitOps](<https://devfeed.tech/topics/gitops.md>), [Argo CD](<https://devfeed.tech/topics/argo-cd.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [flux](<https://devfeed.tech/topics/flux.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [airbnb](<https://devfeed.tech/tags/airbnb.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [cache](<https://devfeed.tech/tags/cache.md>), [churn](<https://devfeed.tech/tags/churn.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [continuous-deployment](<https://devfeed.tech/tags/continuous-deployment.md>), [controller](<https://devfeed.tech/tags/controller.md>), [convergence](<https://devfeed.tech/tags/convergence.md>), [crd](<https://devfeed.tech/tags/crd.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [devops](<https://devfeed.tech/tags/devops.md>), [diversity](<https://devfeed.tech/tags/diversity.md>), [engine](<https://devfeed.tech/tags/engine.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-argocd-linkedin](<https://devfeed.tech/tags/kubernetes-argocd-linkedin.md>), [kubernetes-clusters](<https://devfeed.tech/tags/kubernetes-clusters.md>), [linkedin](<https://devfeed.tech/tags/linkedin.md>), [news](<https://devfeed.tech/tags/news.md>)

### AI overview

LinkedIn replaced Argo CD for application deployments with an internal GitOps engine that runs each deployment in an isolated, ephemeral pod, uses full-object PUTs, retries resource-version conflicts, and checks drift with a three-way diff. The system supports 4,000+ services across 250+ Kubernetes clusters and handles over 100,000 deployments weekly. In a year-over-year comparison, deployment-system failures fell from 925 to 63 as deployment volume rose 3.7x, and median detection and resolution time fell from 16.1 to 2.45 minutes. LinkedIn cautions that improvements also reflect better orchestrator reliability and error classification; successful-deployment median duration stayed similar, while mean and tail improved. Argo CD remains in use for add-ons and system services, and the internal engine has no stated open-source release. Unlike LinkedIn's per-deployment pods, Uber uses a long-running controller per deployment; Airbnb's kube-gen tooling applies or replaces objects and treats a rollout container restarting for 30 seconds as failure. The comparison excludes drift errors and uses May 2026 as the first clean post-migration month.

### Source excerpt

In a recent post, LinkedIn revealed it has replaced Argo CD with its own GitOps engine. This new system deploys applications across over 250 Kubernetes clusters. It supports more than 4,000 services and manages over 100,000 deployments each week. By Claudio Masolo

## How Flickr modernized caching with Amazon ElastiCache for Valkey

DevFeed: [How Flickr modernized caching with Amazon ElastiCache for Valkey](<https://devfeed.tech/articles/how-flickr-modernized-caching-with-amazon-elasticache-for-valkey-129585.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-flickr-modernized-caching-with-amazon-elasticache-for-valkey/>)

Author: Wilson Lam

Published: 2026-11-11T15:54:48Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [all](<https://devfeed.tech/tags/all.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [end-user](<https://devfeed.tech/tags/end-user.md>), [failover](<https://devfeed.tech/tags/failover.md>), [layer](<https://devfeed.tech/tags/layer.md>), [more](<https://devfeed.tech/tags/more.md>), [moving](<https://devfeed.tech/tags/moving.md>), [over](<https://devfeed.tech/tags/over.md>), [post](<https://devfeed.tech/tags/post.md>), [redis](<https://devfeed.tech/tags/redis.md>), [team](<https://devfeed.tech/tags/team.md>), [this](<https://devfeed.tech/tags/this.md>), [user](<https://devfeed.tech/tags/user.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Flickr moved more than 40 Redis clusters behind Twemproxy to cluster-mode Amazon ElastiCache for Valkey deployments, replacing Predis with PhpRedis and enabling multi-AZ automatic failover. Valkey's Redis OSS API compatibility through version 7.2 allowed an in-place engine swap without application changes or data migration. For topology changes, Flickr rolled out workload by workload, starting with regenerable data; data-sensitive workloads were copied with RIOT, using scan mode for bulk replication and live mode to keep data synchronized. A rollout exposed temporarily stale cached content from keys that had not synchronized, prompting targeted database backfill and use of RIOT compare mode before later cutovers. On the most fragmented workload, increasing RIOT threads and reducing batch size resolved stalled replication. After consolidation, Flickr reports monthly ElastiCache spend fell about 5%, despite improved replication and failover; parallel clusters temporarily raised costs during the migration.

### Source excerpt

Flickr, part of SmugMug, serves over 100 million photographers. In this post, the Flickr team shares how they modernized their caching layer by migrating from Redis and Twemproxy to Amazon ElastiCache for Valkey, consolidating more than 40 clusters, enabling cluster mode and multi-AZ failover, and moving to PhpRedis, all with no end-user disruption.

## Platform engineering needs to become more human...and less

DevFeed: [Platform engineering needs to become more human...and less](<https://devfeed.tech/articles/platform-engineering-needs-to-become-more-human-and-less-128942.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/11/11/platform-engineering-needs-to-become-more-humanand-less/>)

Author: Alejandro Chirinos, Control Plane

Published: 2026-11-11T12:00:00Z

Content type: opinion

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [internal developer platform](<https://devfeed.tech/topics/internal-developer-platform.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [platform engineering automation](<https://devfeed.tech/topics/platform-engineering-automation.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [blog](<https://devfeed.tech/tags/blog.md>), [but](<https://devfeed.tech/tags/but.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [family](<https://devfeed.tech/tags/family.md>), [good](<https://devfeed.tech/tags/good.md>), [i](<https://devfeed.tech/tags/i.md>), [job](<https://devfeed.tech/tags/job.md>), [less](<https://devfeed.tech/tags/less.md>), [linear](<https://devfeed.tech/tags/linear.md>), [little](<https://devfeed.tech/tags/little.md>), [logical](<https://devfeed.tech/tags/logical.md>), [me](<https://devfeed.tech/tags/me.md>), [more](<https://devfeed.tech/tags/more.md>), [my](<https://devfeed.tech/tags/my.md>), [needs](<https://devfeed.tech/tags/needs.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [robotic](<https://devfeed.tech/tags/robotic.md>), [that-s](<https://devfeed.tech/tags/that-s.md>)

### AI overview

Platform engineering should accommodate both less technical human builders and fast, instruction-following agents by moving safety rules into the platform. For human users, the article recommends creating narrowly scoped app identities, injecting secrets at runtime, checking every change against policy, using small monitored deployments that roll back when needed, and explaining rejections in plain language. For agents, it calls for separate identities tied to their launcher, task-scoped expiring permissions, caps on changes, resources and spending, preview environments, audit trails, and a quickly accessible kill switch. Agents also need machine-readable rules and structured rejection reasons. The article uses Kubernetes as a model: declare desired outcomes, reconcile continuously, admit all requests through the same policy checks, set quotas, and assume failures will require gradual rollout or rollback. These are recommendations, not reported implementation results.

### Source excerpt

Even my family thinks I'm a little robotic. Logical, linear, sequential, methodical. But hey, I'm an engineer, and that's part of what makes me good at my job. If I were operating on the same volatile...

## Static Publishing on Fastly Compute: What's New in v8

DevFeed: [Static Publishing on Fastly Compute: What's New in v8](<https://devfeed.tech/articles/static-publishing-on-fastly-compute-what-s-new-in-v8-129259.md>)

Original publisher: [Read original article](<https://www.fastly.com/blog/static-publishing-fastly-compute-whats-new-v8/>)

Author: Katsuyuki Omuro

Published: 2026-11-11T00:00:00Z

Content type: article

Language: en

Sources: [Fastly Blog](<https://devfeed.tech/sources/fastly-blog.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [2-0-0](<https://devfeed.tech/tags/2-0-0.md>), [2022](<https://devfeed.tech/tags/2022.md>), [collections](<https://devfeed.tech/tags/collections.md>), [compute](<https://devfeed.tech/tags/compute.md>), [edge](<https://devfeed.tech/tags/edge.md>), [fastly](<https://devfeed.tech/tags/fastly.md>), [js](<https://devfeed.tech/tags/js.md>), [object](<https://devfeed.tech/tags/object.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [preview](<https://devfeed.tech/tags/preview.md>), [publishing](<https://devfeed.tech/tags/publishing.md>), [serve](<https://devfeed.tech/tags/serve.md>), [static](<https://devfeed.tech/tags/static.md>), [storage](<https://devfeed.tech/tags/storage.md>), [support](<https://devfeed.tech/tags/support.md>), [urls](<https://devfeed.tech/tags/urls.md>), [v8](<https://devfeed.tech/tags/v8.md>), [version](<https://devfeed.tech/tags/version.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Version 8 of `@fastly/compute-js-static-publish` serves static sites from Fastly Compute while keeping content separate from the app, so content updates do not require rebuilding the Wasm app. KV Store remains the default: it deduplicates files by content hash and chunks files over 20 MB. Version 8 adds beta support for Fastly Object Storage or S3-compatible storage, where files remain whole and storage costs may be lower. Named collections allow staging and preview versions to coexist, expire, and be promoted to live; the app can select a collection by hostname, cookie, header, path, or Config Store value. Publishing compresses text files and skips unchanged files; optional response caching avoids storage reads on hits, with responses over 8 MiB served directly from storage by default. The generated JavaScript app can be extended with custom request handling. Upgrading from v6 or earlier requires re-scaffolding; v7 KV Store users can install v8 and rebuild/deploy without republishing existing content.

### Source excerpt

Version 8 of Compute JS Static Publish adds Object Storage support, named collections, and preview URLs. Serve static sites from the edge with no origin.

## Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey

DevFeed: [Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey](<https://devfeed.tech/articles/topstep-s-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey-123996.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/topsteps-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey/>)

Author: Gbeminiyi Abolarin

Published: 2026-11-09T16:59:06Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [cname](<https://devfeed.tech/tags/cname.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [migration](<https://devfeed.tech/tags/migration.md>), [oss](<https://devfeed.tech/tags/oss.md>), [redis](<https://devfeed.tech/tags/redis.md>), [tls](<https://devfeed.tech/tags/tls.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Topstep moved about 53 million keys from a single-node Redis OSS 7.4 instance to a Multi-AZ Amazon ElastiCache for Valkey 7.2.6 cluster using RedisShake in PSYNC mode. Since its source version fell outside the managed migration's supported range and the team required a blue/green rollback path, it replicated commands across peered VPCs, validated key counts and application behavior, then cut over by changing a Route 53 record. The change took seconds; the source remained available during a soak period. Valkey's protocol compatibility avoided code changes apart from TLS configuration. Because the custom DNS name did not match the cluster certificate, Topstep kept CA verification enabled while validating against an allowlist of AWS endpoint names. The team reports automatic Multi-AZ failover, managed patching and backups, read P99 latency around 1.25 ms and write P99 around 0.5 ms, and 1-2 engineer-days per month freed from maintenance.

### Source excerpt

Topstep migrated roughly 53 million keys from self-managed Redis OSS to a fully managed, Multi-AZ Amazon ElastiCache for Valkey cluster. Using RedisShake and a single Amazon Route 53 DNS change, the team completed a blue/green cutover in seconds with no application code changes beyond a small TLS configuration update.

## Why Transactional Emails Fail After Deployment: A Practical Debugging Guide for Developers

DevFeed: [Why Transactional Emails Fail After Deployment: A Practical Debugging Guide for Developers](<https://devfeed.tech/articles/why-transactional-emails-fail-after-deployment-a-practical-debugging-guide-for-developers-123751.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/why-transactional-emails-fail-after-deployment-a-practical-debugging-guide-for-developers/>)

Author: Saifullah Adenwalla

Published: 2026-11-09T11:06:03Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [programming-tips](<https://devfeed.tech/topics/programming-tips.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [acceptance](<https://devfeed.tech/tags/acceptance.md>), [account](<https://devfeed.tech/tags/account.md>), [agile-development](<https://devfeed.tech/tags/agile-development.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [api](<https://devfeed.tech/tags/api.md>), [apple](<https://devfeed.tech/tags/apple.md>), [application](<https://devfeed.tech/tags/application.md>), [application-development](<https://devfeed.tech/tags/application-development.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [async](<https://devfeed.tech/tags/async.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-tokens](<https://devfeed.tech/tags/authentication-tokens.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [developers](<https://devfeed.tech/tags/developers.md>), [fail](<https://devfeed.tech/tags/fail.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [guide](<https://devfeed.tech/tags/guide.md>), [html-css](<https://devfeed.tech/tags/html-css.md>), [practical](<https://devfeed.tech/tags/practical.md>)

### AI overview

A successful SMTP or provider API response confirms submission, not inbox placement. The guide recommends tracing each stage with structured logs and provider message IDs while avoiding sensitive values, then checking application logic, credentials, reset URLs, queues and provider responses. For delivery problems, inspect SPF, DKIM and DMARC records; test rendering, links and plain text across email clients; and use Mailpit or Mailtrap to capture development messages safely. In production, monitor queue failures, retries, delivery events, bounces and complaints. Google Postmaster Tools reports on domain reputation, spam rates and authentication when sending volume supports meaningful data; Can I Email documents client feature support. Checks target different failure layers and do not guarantee inbox delivery; setup should match the application's volume and complexity.

### Source excerpt

null Continue reading Why Transactional Emails Fail After Deployment: A Practical Debugging Guide for Developers on SitePoint.

## Catch incidents and pause faulty deployments automatically with Datadog Deployment Gates

DevFeed: [Catch incidents and pause faulty deployments automatically with Datadog Deployment Gates](<https://devfeed.tech/articles/catch-incidents-and-pause-faulty-deployments-automatically-with-datadog-deployment-gates-126557.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/deployment-gates/>)

Author: Eric Metaj; Mike Leach

Published: 2026-11-09T00:00:00Z

Content type: release

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [blue green and canary deployments](<https://devfeed.tech/topics/blue-green-and-canary-deployments.md>), [datadog](<https://devfeed.tech/topics/datadog.md>), [Argo Rollouts](<https://devfeed.tech/topics/argo-rollouts.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [ai-engine](<https://devfeed.tech/tags/ai-engine.md>), [api](<https://devfeed.tech/tags/api.md>), [apm](<https://devfeed.tech/tags/apm.md>), [application](<https://devfeed.tech/tags/application.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [canary-releases](<https://devfeed.tech/tags/canary-releases.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [customer](<https://devfeed.tech/tags/customer.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deployment-gates](<https://devfeed.tech/tags/deployment-gates.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [devops](<https://devfeed.tech/tags/devops.md>), [faster](<https://devfeed.tech/tags/faster.md>), [impact](<https://devfeed.tech/tags/impact.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [limit](<https://devfeed.tech/tags/limit.md>), [production](<https://devfeed.tech/tags/production.md>), [software-delivery](<https://devfeed.tech/tags/software-delivery.md>)

### AI overview

Datadog Deployment Gates evaluates production health after a deployment or between rollout stages and can pause the workflow when a required check fails. Teams can use existing Datadog monitors for conditions such as errors, latency, and resource use, alongside Watchdog Faulty Deployment Detection, which compares APM-instrumented service versions to flag new error types or significant endpoint error-rate increases that configured monitors may miss. Gates can be added through GitHub Actions, Argo Rollouts, datadog-ci, or the Datadog API. Dry-run mode records which deployments would pause and why while allowing them to continue; active mode pauses on failed checks. Datadog links failures to monitor or APM findings and related traces, with Bits Chat available to explore causes and next steps. Evaluation history helps teams review recurring failures and trends.

### Source excerpt

Automate deployment checks with Datadog Deployment Gates to catch production issues, limit customer impact, and investigate faster.

[Next page](<https://devfeed.tech/topics/deployment-strategies.md?cursor=WyIyMDI2LTExLTA5VDAwOjAwOjAwKzAwOjAwIiwgIjBlYTQyMzkzLWJmOGItNDhkMi05MjhlLTg2YjgyMzlmZGIxYSJd>)