---
title: "Migration toolkit for applications 8.3: Agentic code modernization, PVC mobility, and out-of-the-box generators"
description: "Red Hat’s migration toolkit for applications 8.3 is now generally available, adding agentic code modernization, direct storage mobility, and automated pipeline generation to OpenShift. The release serves as the official transition path from the migration toolkit for containers, which has reached end of support. For stateful workloads, it introduces direct TLS-encrypted persistent volume claim transfers with a stage-and-cutover flow, S3-mediated indirect transfers for disconnected environments, and intra-cluster StorageClass conversions that bypass Kubernetes immutability constraints. A developer preview agentic migration factory runs configurable multi-agent workflows that analyze dependencies, update code, and validate builds across independent stages, passing context through handoff files on shared Git branches. The toolkit also ships three new Helm-based generators that produce Tekton pipelines, Argo CD Application resources, and Kubernetes deployment manifests for onboarded applications."
---

# Migration toolkit for applications 8.3: Agentic code modernization, PVC mobility, and out-of-the-box generators

[Red Hat](https://yomu.fyi/company/red-hat) · Syed M Shaaf, Ramon Roman Nissen · Oct 8, 2026

**Type:** Announcement

## Summary

Red Hat’s migration toolkit for applications 8.3 is now generally available, adding agentic code modernization, direct storage mobility, and automated pipeline generation to OpenShift. The release serves as the official transition path from the migration toolkit for containers, which has reached end of support. For stateful workloads, it introduces direct TLS-encrypted persistent volume claim transfers with a stage-and-cutover flow, S3-mediated indirect transfers for disconnected environments, and intra-cluster StorageClass conversions that bypass Kubernetes immutability constraints. A developer preview agentic migration factory runs configurable multi-agent workflows that analyze dependencies, update code, and validate builds across independent stages, passing context through handoff files on shared Git branches. The toolkit also ships three new Helm-based generators that produce Tekton pipelines, Argo CD Application resources, and Kubernetes deployment manifests for onboarded applications.

## Context

Upgrading workloads to cloud-native architectures often means struggling with legacy code and complex stateful data transfers. The migration toolkit for containers has reached end of support, making migration toolkit for applications 8.3 the official transition path for container migration on OpenShift.

## Approach / What changed

Migration toolkit for applications 8.3 automates the container migration lifecycle with direct TLS-encrypted PVC transfers using a stage-and-cutover flow, S3-mediated indirect migrations for air-gapped networks, and intra-cluster StorageClass conversions. It adds an agentic migration factory that runs configurable multi-agent workflows with handoff files on shared Git branches, and ships three Helm-based generators (Tekton pipelines, Argo CD Application resources, Java Service manifests) for day-one CI/CD and GitOps deployment.

## Takeaways

- Direct PVC transfers use a stage-and-cutover flow: most data syncs while the application stays live, then a brief delta transfer occurs during cutover, all over TLS-encrypted tunnels.
- Intra-cluster StorageClass conversion clones volume data to a newly provisioned PVC, and workloads automatically re-bind to the new volume without manual manifest editing, enabling zero-downtime migration to CSI drivers.
- The agentic migration factory runs agents in secure sandboxes with strict policy, RBAC, and audit boundaries, with credentials completely isolated from agent processes and configurable maximum context windows to prevent LLM overflow.

## FAQ

### How does the stage-and-cutover PVC transfer work?

Most data is synced while the application stays live, then a brief delta transfer occurs during cutover. The transfer happens over TLS-encrypted tunnels between clusters.

### How is context passed between agent stages?

Each stage runs an agent that completes a specific task, and context is passed between stages through a handoff file on a shared Git branch, enabling iterative code resolutions.

### What does the Java Service Generator produce?

It produces Kubernetes deployment manifests and a multi-stage Containerfile for Spring Boot and Quarkus (JVM) applications.

**Tags:** [AI Agents](https://yomu.fyi/topic/ai-agents), [CI/CD](https://yomu.fyi/topic/ci-cd), [Kubernetes](https://yomu.fyi/topic/kubernetes), [Migrations](https://yomu.fyi/topic/migration), [Red Hat OpenShift](https://yomu.fyi/topic/red-hat-openshift)

- Source: [Red Hat](https://developers.redhat.com/articles/2026/10/08/migration-toolkit-applications-8-3-agentic-code-modernization)
- Source URL: https://developers.redhat.com/articles/2026/10/08/migration-toolkit-applications-8-3-agentic-code-modernization
- Ingested by Yomu: 2026-10-08T15:00:14.792Z

[Read original post](https://developers.redhat.com/articles/2026/10/08/migration-toolkit-applications-8-3-agentic-code-modernization)