Anypoint Runtime Fabric 3.x.x Release Notes
These are the release notes for Runtime Fabric v3.x.x.
For the complete Runtime Fabric documentation, refer to Anypoint Runtime Fabric.
To maintain compatibility and system integrity, customers using a private registry must synchronize the rtf-mule-actions image, refer to Runtime Fabric Mule Action Image Synchronization for details.
This table shows Kubernetes supported versions:
| K8s version | Upstream K8s GA | Runtime Fabric Support GA | Runtime Fabric Support EOL |
|---|---|---|---|
1.24 |
May 2022 |
January 2023 |
February 2024 |
1.25 |
August 2022 |
May 2023 |
June 2024 |
1.26 |
December 2022 |
June 2023 |
May 2024 |
1.27 |
April 2023 |
November 2023 |
January 2025 |
1.28 |
August 2023 |
March 2024 |
June 2025 |
1.29 |
December 2023 |
June 2024 |
October 2025 |
1.30 |
May 2024 |
October 2024 |
Runtime Fabric support of 1.34 |
1.31 |
August 2024 |
January 2025 |
Runtime Fabric support of 1.35 |
1.32 |
December 2024 |
June 2025 |
Runtime Fabric support of 1.36 |
1.33 |
April 2025 |
October 2025 |
Runtime Fabric support of 1.37 |
3.0.1
December 8, 2025
What’s New
-
Runtime Fabric agent version 3.0.1 now supports Anypoint Controller for Kubernetes. This operator enables you to deploy and manage Mule applications on Runtime Fabric using GitOps workflows and Custom Resources (CR).
-
This feature is currently in Limited General Availability (Limited GA).
-
To enable Anypoint Controller for your organization, contact MuleSoft Support.
For details, refer to Deploying and Managing Mule Applications Using Anypoint Controller for Kubernetes.
-
-
Runtime Fabric agent version 3.0.1 now supports Mule app restart. You can restart applications to resolve runtime issues such as memory leaks or unresponsive services without redeploying. All restart activities are tracked in the Access Management audit log.
For details, refer to Restarting Mule Applications on Runtime Fabric.
-
Runtime Fabric agent version 3.0.1 removes support for the legacy DaemonSet-based log forwarding method. Application logs are now forwarded exclusively through sidecar containers deployed alongside each application replica, providing better isolation and improved resource management.
For details, refer to Log Forwarding in Runtime Fabric 3.0.1.
-
These dependencies are updated for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:3.0.1 -
coreAction:
mulesoft/rtf-core-actions:1.0.177 -
clusterOps:
mulesoft/rtf-cluster-ops:2.0.266 -
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:1.4.39 -
appInit:
mulesoft/rtf-app-init:1.0.222 -
persistenceGateway:
mulesoft/rtf-object-store:1.0.242 -
resourceFetcher:
mulesoft/rtf-resource-fetcher:1.0.228 -
rtfDaemon:
mulesoft/rtf-daemon:2.0.218 -
Base Image Nginx:
mulesoft/supply-chain-nginx-base-image:3.1.40
-
-
These dependencies are updated for installing Runtime Fabric as a Kubernetes (K8s) operator:
-
Ubi agent version:
mulesoft/rtf-agent-ubi:3.0.1 -
Ubi coreAction:
mulesoft/rtf-core-actions-ubi:1.0.177 -
Ubi clusterOps:
mulesoft/rtf-cluster-ops-ubi:2.0.266 -
Ubi muleClusterIpService:
mulesoft/rtf-mule-clusterip-service-ubi:1.4.39 -
Ubi appInit:
mulesoft/rtf-app-init-ubi:1.0.222 -
Ubi persistenceGateway:
mulesoft/rtf-object-store-ubi:1.0.242 -
Ubi resourceFetcher:
mulesoft/rtf-resource-fetcher-ubi:1.0.228 -
Ubi rtfDaemon:
mulesoft/rtf-daemon-ubi:2.0.218 -
Ubi Base Nginx:
mulesoft/rtf-ubi-base-nginx:0.3.30
-
Fixed Issues
| Issue Resolution | ID |
|---|---|
This release includes security fixes. |
W-20141521 |
Applying a trust anchor (certificate) for a local, self-signed registry now works correctly on Runtime Fabric, ensuring the Runtime Fabric agent can establish trust. |
W-16483594 |
Deploying updated applications using the Mule Maven Plugin 4.6.0 with a |
W-20077300 |
Excessive process accumulation in readiness probes no longer occurs, ensuring more stable application startup. |
W-19853421 |