Anypoint Control Plane, all Runtime Fabric agents must be upgraded to version 2.11.50 or later by March 31, 2026

To maintain secure and uninterrupted connectivity with the Anypoint Control Plane, all Runtime Fabric agents must be upgraded to version 2.11.50 or later by March 31, 2026. After that date, earlier versions will no longer be connected to the control plane.

Why This Matters

The upgraded version 2.11.50 includes critical improvements to Runtime Fabric agent stability, control plane handshake protocols, and future platform compatibility. Upgrading ensures your environment remains compliant and operational.

Call to Action

1. By March 31, 2026, upgrade to version 2.11.50 or later.

What You Need to Do

1. Run this command to check your current agent version (rtfctl maybe run from anywhere you have network access to the k8s control plane running RTF and a valid kubeconfig):

rtfctl version

2. Review the Upgrade Guide for step-by-step instructions. 

3. Schedule your upgrade and validate post-upgrade connectivity.

If you have any questions or need assistance, please submit a ticket via the Anypoint Support Portal or contact your MuleSoft Customer Success Manager.

• Applications that are already running are expected to continue processing traffic without interruption
• No application redeployments or restarts are triggered solely by the agent upgrade

• New application deployments, redeployments, or configuration changes cannot be performed
• Scaling operations and policy updates are unavailable
• Application status, logs, and metrics updates may not be visible in Anypoint Runtime Manager
• Operational actions requiring communication with Anypoint Platform will be paused

FAQs:

1. Do I need to redeploy my applications as part of this upgrade?

No. You do not need to redeploy the applications. Runtime Fabric agent runs as a separate pod in your cluster and is upgraded independently of your applications. 

2. During upgrade, would there be any impact to my applications?

No. You application would continue to serve traffic. However, during upgrade as the RTF agent is temporarily unavailable or restarting, certain management capabilities are limited. Specifically, 

• New application deployments, redeployments, or configuration changes cannot be performed

• Scaling operations and policy updates are unavailable

• Application status, logs, and metrics updates may not be visible in Anypoint Runtime Manager

• Operational actions requiring communication with Anypoint Platform will be paused

3. If I fail to upgrade by the scheduled date and the RTF agent disconnects, would my applications fail to serve traffic?

No. Your applications would continue to serve traffic. However,  you may not be able to scale your application replicas, either manually or through autoscaling, to serve the increasing traffic. 

4. What Kubernetes versions are supported by RTF v2.11.50?

RTF v2.11.50 supports Kubernetes versions 1.30, 1.31, 1.32, and 1.33

5. Can I directly upgrade from any 2.x version of RTF to v2.11.50?

Yes. You can upgrade directly from any 2.x version. However, you will need to upgrade your Kubernetes version as well if you are running Kubernetes versions lower than 1.30.

6. Do I need to be on any specific Mule runtime version before upgrading to RTF v2.11.50?

No. RTF v2.11.50 does not require you to be on any specific Mule runtime versions.