MuleSoft Runtime Fabric Migration to Self-Managed Kubernetes

Migrate Runtime Fabric to Self-Managed Kubernetes with Confidence

Migrating from Anypoint Runtime Fabric on VMs or Bare Metal to Self-Managed Kubernetes (SMK) is a significant step because it impacts multiple layers of the platform. It touches infrastructure, applications, operations, and long-term platform support. We understand that this kind of migration needs careful planning, not rushed execution. This transition involves Runtime Fabric migration within MuleSoft environments and requires a structured, low-risk approach.

At NJC Labs, we guide organizations through this journey from early assessment to post-migration stabilization , in a phased and controlled manner. Our teams stay closely involved to reduce risk, maintain platform stability, and at the same time, ensure your Runtime Fabric environment is ready for long-term growth on Kubernetes.

What We Help You Migrate

We support complete Runtime Fabric migration from legacy infrastructure models into modern Kubernetes environments, while at the same time avoiding disruption to business operations. This includes aligning Runtime Fabric with supported Kubernetes distributions, in addition to configuring networking, storage, and observability to meet enterprise standards. We also help teams adapt to the shared responsibility model of Runtime Fabric, clarifying what MuleSoft manages versus what your platform teams own.

Runtime Fabric on VMs to SMK

RTF deployments on virtual machines often face scaling and lifecycle challenges, especially as environments grow over time. We migrate these environments to Self-Managed Kubernetes, as a result improving orchestration, resilience, and operational consistency.

Runtime Fabric on Bare Metal to SMK

Bare metal offers performance, however, it also increases operational complexity. We help transition Runtime Fabric on Bare Metal to Kubernetes while preserving security, performance, and governance.

Why Runtime Fabric Migration Is Critical Now?

MuleSoft’s Runtime Fabric VM and Appliance deployment model has entered Extended Support. According to MuleSoft’s lifecycle policy:

End of Life: 1st February 2024
End of Support: 1st February 2025

Remaining on these deployment models beyond support timelines significantly increases security, compliance, and operational risk. More importantly, it limits your ability to upgrade, scale, and adopt newer MuleSoft capabilities in the long run. Because of these support changes, MuleSoft Runtime Fabric migration becomes essential for organizations that want to reduce risk and stay aligned with the platform’s future roadmap. Migrating to Self-Managed Kubernetes (SMK) ensures your Runtime Fabric remains fully supported, future-ready, and aligned with MuleSoft’s strategic direction.

Why Migrate to Self-Managed Kubernetes (SMK)

Customization & Control

Full control over configuration and cluster behaviour, as a result, allows performance to be tailored more effectively to your workloads.

Cost & Performance Efficiency

Self-managed Kubernetes can reduce long-term costs while, at the same time, enabling fine-tuned performance and reliability.

Hybrid & Multi-Cloud Flexibility

SMK supports hybrid and multi-cloud strategies, providing portability across environments.

Compliance & Security

Greater control over security and compliance configurations, especially important for regulated industries.

Our Migration Approach

Assessment & Target Architecture

We assess your current Runtime Fabric setup and identify the right Kubernetes target environment, based on this assessment, selecting the appropriate Kubernetes distribution in line with expertise and compliance needs.

Kubernetes Cluster Setup & Security

We set up the Kubernetes cluster and configure networking, routing, storage, and security, thereby ensuring the environment is production-ready before workloads are migrated.

Data Migration & Secrets Management

We plan and execute data migration using Persistent Gateways or cloud storage where appropriate, ensuring continuity during the migration process. Sensitive data such as API keys and credentials is securely managed using Kubernetes Secrets.

Discovery, Load Balancing & Observability

We configure Kubernetes Services, Ingress Controllers, and implement monitoring and logging, in turn providing visibility into application health, performance, and resource usage.

Testing & Validation

Migrated applications undergo functional, load, and performance testing before go-live, ensuring the Kubernetes environment can handle real production traffic.

Deployment, Training & Optimization

Applications are migrated using a phased deployment approach so that disruption is minimised across environments. Post-migration, we train teams and optimise performance, and cost efficiency.

Supported Kubernetes Platforms

Runtime Fabric supports the following Kubernetes platforms:

- Amazon Elastic Kubernetes Service (EKS)
- Amazon EKS Anywhere (EKS-A)
- Google Kubernetes Engine (GKE)
- Azure Kubernetes Service (AKS)
- Red Hat OpenShift Service on AWS (ROSA)
- Azure Red Hat OpenShift (ARO)
- Red Hat OpenShift Dedicated on GCP
- Red Hat Openshift on IBM Cloud
- Red Hat Openshift Kubernetes Engine (Entry Level)
- Red Hat Openshift Container Platform (OCP)
- Red Hat Openshift Platform Plus

Why NJC Labs for Runtime Fabric Migration?

Anypoint Runtime Fabric operates on a shared responsibility model where MuleSoft provides the platform, by design, while infrastructure and operations remain with your organization. NJC Labs helps you clearly define and manage this responsibility, thereby ensuring nothing is missed during or after migration. By combining deep MuleSoft Runtime Fabric and Kubernetes expertise with a people-first approach, we support developers, platform teams, and business continuity throughout the journey. We listen carefully, plan thoroughly, and stay engaged until your environment is stable, supported, and future-ready, guiding the migration at the right pace, not rushing it.

Frequently Asked Questions

1. Why do we need to migrate Runtime Fabric now?

MuleSoft’s Runtime Fabric VM and Appliance model has entered Extended Support, with End of Life on 1st February 2024 and End of Support on 1st February 2025. Migrating early helps reduce security, compliance, and operational risk while avoiding last-minute, high-pressure upgrades.

2. What is Runtime Fabric (RTF) migration?

Runtime Fabric migration involves moving MuleSoft workloads from Runtime Fabric on VMs or Bare Metal to a Self-Managed Kubernetes (SMK) environment. This ensures your platform remains supported, scalable, and aligned with MuleSoft’s future direction.

3. Will Runtime Fabric migration cause downtime?

In most cases, no. We use phased migrations, parallel environments, and controlled cutovers to minimize or eliminate downtime and protect business continuity.

4. Do we need Kubernetes expertise in-house to migrate?

Not initially. NJC Labs supports the entire journey, from planning and execution to stabilization and training – so your teams can gradually build Kubernetes confidence over time.

5. Do you provide support after RTF migration?

Yes. We offer post-migration hypercare, monitoring, optimization, governance setup, and optional managed services to ensure long-term stability.

Start Your RTF Migration the Right Way

Is your Runtime Fabric environment nearing end of support or becoming harder to manage?

NJC Labs supports you from assessment to stabilization, ensuring your RTF migration is secure, compliant, and aligned with MuleSoft’s future roadmap.

MuleSoft RTF Migration Services