1. Homepage
  2. Release Notes

  3. Anypoint Runtime Fabric 3.x.x Release Notes

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.35

December 2025

Before July 31, 2026

Runtime Fabric support of 1.39

1.34

April 2025

March 2026

Runtime Fabric support of 1.38

1.33

April 2025

October 2025

Runtime Fabric support of 1.37

1.32

December 2024

June 2025

Runtime Fabric support of 1.36

1.31

August 2024

January 2025

Runtime Fabric support of 1.35

1.30

May 2024

October 2024

Runtime Fabric support of 1.34

1.29

December 2023

June 2024

October 2025

1.28

August 2023

March 2024

June 2025

1.27

April 2023

November 2023

January 2025

1.26

December 2022

June 2023

May 2024

1.25

August 2022

May 2023

June 2024

1.24

May 2022

January 2023

February 2024

3.0.102

May 28, 2026

What’s New

  • The Anypoint Runtime Manager UI now supports handlebar-style placeholders (such as {{ .ApplicationName }}) when configuring public endpoints for HTTP route templates. Runtime Manager replaces placeholders that you enter in host or path fields with deployment-specific values at deployment time. The Runtime Manager UI now treats legacy ingress-style strings such as app-name as literal strings, not as placeholders, for HTTP route templates.

    For details, refer to HTTP Route-Template Custom-Resource Placeholders.

  • Supported keys for pod.env field in the Anypoint Controller

    When deploying Mule applications using the Anypoint Controller CR (MuleApplication), the pod.env field in the CR spec supports only these keys:

    • ENABLE_CONSOLE_LOG: Enables console logging for the application container.

    • ENABLE_READINESS_PROBE_ON_HTTP_GET: Enables the native Kubernetes HTTP GET readiness probe (requires Mule runtime patches from November 7, 2025 or later).

    • DISABLE_PER_APP_SA: Disables the per-application service account, causing the Mule application to use the default namespace service account.

      For further details, refer to Kubernetes Customization.

  • These dependencies are updated for installing and managing Runtime Fabric with a local registry:

    • agent version: mulesoft/rtf-agent:3.0.102

    • coreAction: mulesoft/rtf-core-actions:1.0.200

    • clusterOps: mulesoft/rtf-cluster-ops:2.0.299

    • muleClusterIpService: mulesoft/rtf-mule-clusterip-service:1.4.52

    • appInit: mulesoft/rtf-app-init:1.0.245

    • persistenceGateway: mulesoft/rtf-object-store:1.0.264

    • resourceFetcher: mulesoft/rtf-resource-fetcher:1.0.259

    • rtfDaemon: mulesoft/rtf-daemon:2.0.284

    • Base Image Nginx: mulesoft/supply-chain-nginx-base-image:3.1.44

  • These dependencies are updated for installing Runtime Fabric as a Kubernetes (K8s) operator:

    • Ubi agent version: mulesoft/rtf-agent-ubi:3.0.102

    • Ubi coreAction: mulesoft/rtf-core-actions-ubi:1.0.200

    • Ubi clusterOps: mulesoft/rtf-cluster-ops-ubi:2.0.299

    • Ubi muleClusterIpService: mulesoft/rtf-mule-clusterip-service-ubi:1.4.52

    • Ubi appInit: mulesoft/rtf-app-init-ubi:1.0.245

    • Ubi persistenceGateway: mulesoft/rtf-object-store-ubi:1.0.264

    • Ubi resourceFetcher: mulesoft/rtf-resource-fetcher-ubi:1.0.259

    • Ubi rtfDaemon: mulesoft/rtf-daemon-ubi:2.0.284

    • Ubi Base Nginx: mulesoft/rtf-ubi-base-nginx:0.3.48

Fixed Issues

Issue Resolution ID

Third-party dependency updates now improve Runtime Fabric stability and compatibility.

W-22371736

Timing-related failures no longer prevent applications created by Anypoint Controller from being deleted.

W-22200626

FIPS-compliant deployments now apply the correct binary flags consistently.

W-22265793, W-22348521

rtfctl installations now create the am-monitoring-certificate secret automatically.

W-21562809

Supported Kubernetes Versions

Runtime Fabric version 3.0.102 supports these Kubernetes versions:

  • 1.34.x

  • 1.33.x

  • 1.32.x

  • 1.31.x

3.0.43

March 11, 2026

What’s New

  • Runtime Fabric agent version 3.0.43 now supports Kubernetes (K8s) 1.34.

  • These dependencies are updated for installing and managing Runtime Fabric with a local registry:

    • agent version: mulesoft/rtf-agent:3.0.43

    • coreAction: mulesoft/rtf-core-actions:1.0.178

    • clusterOps: mulesoft/rtf-cluster-ops:2.0.273

    • muleClusterIpService: mulesoft/rtf-mule-clusterip-service:1.4.41

    • appInit: mulesoft/rtf-app-init:1.0.225

    • persistenceGateway: mulesoft/rtf-object-store:1.0.246

    • resourceFetcher: mulesoft/rtf-resource-fetcher:1.0.233

    • rtfDaemon: mulesoft/rtf-daemon:2.0.246

    • Base Image Nginx: mulesoft/supply-chain-nginx-base-image:3.1.42

  • These dependencies are updated for installing Runtime Fabric as a Kubernetes (K8s) operator:

    • Ubi agent version: mulesoft/rtf-agent-ubi:3.0.43

    • Ubi coreAction: mulesoft/rtf-core-actions-ubi:1.0.178

    • Ubi clusterOps: mulesoft/rtf-cluster-ops-ubi:2.0.273

    • Ubi muleClusterIpService: mulesoft/rtf-mule-clusterip-service-ubi:1.4.41

    • Ubi appInit: mulesoft/rtf-app-init-ubi:1.0.225

    • Ubi persistenceGateway: mulesoft/rtf-object-store-ubi:1.0.246

    • Ubi resourceFetcher: mulesoft/rtf-resource-fetcher-ubi:1.0.233

    • Ubi rtfDaemon: mulesoft/rtf-daemon-ubi:2.0.246

    • Ubi Base Nginx: mulesoft/rtf-ubi-base-nginx:0.3.30

Fixed Issues

Issue Resolution ID

This release includes security fixes.

W-20921271

Runtime Fabric application initialization pods no longer fail with Error: checksum validation failed following a Runtime Fabric upgrade. The application init container now correctly detects corrupt or outdated cache artifacts and requests a new version from the upstream.

New or updated deployments automatically receive this fix with the latest Runtime Fabric version. Redeploy existing applications to use the updated init container image and resolve any persistent checksum errors.

W-20383477

Supported Kubernetes Versions

Runtime Fabric version 3.0.43 supports these Kubernetes versions:

  • 1.34.x

  • 1.33.x

  • 1.32.x

  • 1.31.x

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).

    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.

  • When using Runtime Fabric 3.0.1 or later, the HTTP GET readiness probe configuration (which defaults to false) requires your applications to run on Mule runtime engine patches from November 7, 2025, or later. If this feature is enabled for applications on older patches, they may fail to become ready or restart correctly. If you can’t upgrade your runtimes immediately, make sure the feature remains disabled. For details, refer to Readiness Probe.

  • 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 -SNAPSHOT version to Runtime Fabric now correctly deploys the latest asset.

W-20077300

Excessive process accumulation in readiness probes no longer occurs, ensuring more stable application startup.

W-19853421

Supported Kubernetes Versions

Runtime Fabric version 3.0.1 supports these Kubernetes versions:

  • 1.33.x

  • 1.32.x

  • 1.31.x

  • 1.30.x

See Also