---
schema_version: "1"
id: 630bd1f89ab38b99ff222f7e044c077aa3af2b6ff1b4327d5ee275e95be1523d
title: Anypoint Runtime Fabric 2.x.x Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/runtime-fabric/runtime-fabric-release-notes-2.x.x.md
canonical_url: https://docs.mulesoft.com/release-notes/runtime-fabric/runtime-fabric-release-notes-2.x.x
source_site: docs.mulesoft.com
content_type: documentation
content_hash: bccff3587dd9d300268163fe160638c9603e958e19c1bdb288830da460252506
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# Anypoint Runtime Fabric 2.x.x Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The following are release notes for Runtime Fabric v2.x.x.

For the complete Runtime Fabric documentation, refer to
[Anypoint Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/).

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](https://docs.mulesoft.com/release-notes/runtime-fabric/runtime-fabric-rtf-mule-action) for details.

> [!NOTE] Starting September 2022, Runtime Fabric agent releases on the v2.0.0 line apply only to
> partner platforms (both Kubernetes and VMs/Bare Metal). Agent releases for Runtime Fabric
> appliance distributions will continue on the v1.x.x line.

The following table shows Kubernetes supported versions:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>K8s version</th><th>Upstream K8s GA</th><th>Runtime Fabric Support GA</th><th>Runtime Fabric Support EOL</th></tr></thead><tbody><tr><td><p>1.24</p></td><td><p>May 2022</p></td><td><p>January 2023</p></td><td><p>February 2024</p></td></tr><tr><td><p>1.25</p></td><td><p>August 2022</p></td><td><p>May 2023</p></td><td><p>June 2024</p></td></tr><tr><td><p>1.26</p></td><td><p>December 2022</p></td><td><p>June 2023</p></td><td><p>May 2024</p></td></tr><tr><td><p>1.27</p></td><td><p>April 2023</p></td><td><p>November 2023</p></td><td><p>January 2025</p></td></tr><tr><td><p>1.28</p></td><td><p>August 2023</p></td><td><p>March 2024</p></td><td><p>June 2025</p></td></tr><tr><td><p>1.29</p></td><td><p>December 2023</p></td><td><p>June 2024</p></td><td><p>October 2025</p></td></tr><tr><td><p>1.30</p></td><td><p>May 2024</p></td><td><p>October 2024</p></td><td><p>Runtime Fabric support of 1.34</p></td></tr><tr><td><p>1.31</p></td><td><p>August 2024</p></td><td><p>January 2025</p></td><td><p>Runtime Fabric support of 1.35</p></td></tr><tr><td><p>1.32</p></td><td><p>December 2024</p></td><td><p>June 2025</p></td><td><p>Runtime Fabric support of 1.36</p></td></tr><tr><td><p>1.33</p></td><td><p>April 2025</p></td><td><p>October 2025</p></td><td><p>Runtime Fabric support of 1.37</p></td></tr></tbody></table>

## 2.11.50

**October 3, 2025**

### What’s New

- Runtime Fabric agent now supports Kubernetes version 1.33.

- Runtime Fabric agent now supports Oracle Kubernetes Engine (OKE).

- You can now use the MuleSoft diagnostics agent to troubleshoot Mule applications deployed to
  Runtime Fabric. This feature leverages Einstein generative AI to automate diagnostics collection
  and provide intelligent, actionable insights. For details, refer to
  [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/runtime-fabric/latest/view-app-diagnostics).

- These dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.11.50`

  - coreAction: `mulesoft/rtf-core-actions:1.0.173`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.263`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.38`

  - appInit: `mulesoft/rtf-app-init:1.0.218`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.239`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.224`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.189`

  - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.1.38`

- These dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.11.50`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.173`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.263`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.38`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.218`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.239`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.224`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.189`

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

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The resource cache no longer redownloads artifacts from AMC artifacts.</p></div></div></td><td><div><div><p>W-15901814</p></div></div></td></tr><tr><td><div><div><p>The client trust store now correctly trusts the DiGiCert Global Root G3 certificate.</p></div></div></td><td><div><div><p>W-19651269</p></div></div></td></tr><tr><td><div><div><p>This release includes security fixes.</p></div></div></td><td><div><div><p>W-19723504, W-19639371, W-19639220, W-19639164, W-18886584, W-19005736, W-19338580, W-19338562</p></div></div></td></tr></tbody></table>

### Supported Kubernetes Versions

Runtime Fabric version 2.11.50 supports these Kubernetes versions:

- 1.33.x

- 1.32.x

- 1.31.x

- 1.30.x

## 2.11.0

**July 31, 2025**

### What’s New

- You can now
  [configure core software high availability parameters](https://docs.mulesoft.com/runtime-fabric/latest/install-helm#configure-core-software-high-availability-parameters)
  in your `values.yml` file when installing Runtime Fabric using Helm.

- These dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.11.0`

  - coreAction: `mulesoft/rtf-core-actions:1.0.159`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.250`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.31`

  - appInit: `mulesoft/rtf-app-init:1.0.209`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.232`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.220`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.167`

  - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.100`

- These dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.11.0`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.159`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.250`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.31`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.209`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.232`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.220`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.167`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29`

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Invalid memory address or nul pointer dereference no longer occur in Runtime Fabric cluster ops initialization.</p></div></div></td><td><div><div><p>W-19064118</p></div></div></td></tr><tr><td><div><div><p>This release includes security fixes.</p></div></div></td><td><div><div><p>W-19005719</p></div></div></td></tr></tbody></table>

### Supported Kubernetes Versions

Runtime Fabric version 2.11.0 supports these Kubernetes versions:

- 1.32.x

- 1.31.x

- 1.30.x

- 1.29.x

## 2.10.34

**June 30, 2025**

### What’s New

- These dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.10.34`

  - coreAction: `mulesoft/rtf-core-actions:1.0.154`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.245`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.28`

  - appInit: `mulesoft/rtf-app-init:1.0.203`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.230`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.218`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.152`

  - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.95`

- These dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.10.34`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.154`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.245`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.3.120`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.4.28`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.230`

  - Ubi resourceFetcher: ``mulesoft/rtf-resource-fetcher-ubi:`1.0.218``

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.152`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29`

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Runtime Fabric agent now correctly renders OpenShift ingress templates with TLS Edge termination configurations (<code>tls: - {}</code>).</p></div></div></td><td><div><div><p>W-18657349</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric agent now correctly manages and matches ingress templates using wildcards in <code>tls.hosts</code> section.</p></div></div></td><td><div><div><p>W-18472498</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric agent now correctly renders ingress templates with wildcard host and the actual Mule application host from the application deployment configuration, rather than the wildcard pattern.</p></div></div></td><td><div><div><p>W-18839829</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric now supports the deprecated Kubernetes <code>kubernetes.io/ingress.class</code> annotation that was removed in Runtime Fabric agent version 2.10.0. This ensures backward compatibility as you transition to the newer <code>spec.ingressClassName</code> field.</p></div></div></td><td><div><div><p>W-18299600</p></div></div></td></tr><tr><td><div><div><p>Fixed an issue where removed secure properties were not properly deleted from Kubernetes secrets, causing stale data accumulation.</p></div></div></td><td><div><div><p>W-18483799</p></div></div></td></tr><tr><td><div><div><p>Intermittent K8s permission errors that were observed in OpenShift or Runtime Fabric agents with version 2.7.0 and higher no longer occur.</p></div></div></td><td><div><div><p>W-17446390</p></div></div></td></tr></tbody></table>

### Supported Kubernetes Versions

Runtime Fabric version 2.10.34 supports these Kubernetes versions:

- 1.32.x

- 1.31.x

- 1.30.x

- 1.29.x

## 2.10.17

**April 29, 2025**

- These dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.10.17`

  - coreAction: `mulesoft/rtf-core-actions:1.0.148`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.245`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.28`

  - appInit: `mulesoft/rtf-app-init:1.0.203`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.230`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.218`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.139`

  - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.95`

- These dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.10.17`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.148`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.245`

  - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:1.3.120`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.28`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.203`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.220`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.218`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.139`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29`

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Now all matching placeholders in ingress templates are replaced.</p></div></div></td><td><div><div><p>W-17910019</p></div></div></td></tr><tr><td><div><div><p>This release includes security fixes.</p></div></div></td><td><div><div><p>W-18147430, W-18147417, W-17829739</p></div></div></td></tr></tbody></table>

### Supported Kubernetes Versions

Runtime Fabric version 2.10.17 supports these Kubernetes versions:

- 1.31.x

- 1.30.x

- 1.29.x

- 1.28.x

## 2.10.0

**March 25, 2025**

### What’s New

- You can now
  [exclude nodes from Runtime Fabric cluster capacity](https://docs.mulesoft.com/general/usage-metrics#exclude-node).

- These dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.10.0`

  - coreAction: `mulesoft/rtf-core-actions:1.0.142`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.240`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.25`

  - appInit: `mulesoft/rtf-app-init:1.0.201`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.227`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.211`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.135`

  - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.84`

- These dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.10.0`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.142`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.240`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.25`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.201`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.227`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.211`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.135`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29`

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Runtime Fabric agent now correctly consumes the port number configured in the ingress template.</p></div></div></td><td><div><div><p>W-17624273</p></div></div></td></tr><tr><td><div><div><p>Mule apps created from an HTTP ingress template are no longer forced to use HTTPS due to the inclusion of an empty TLS block.</p></div></div></td><td><div><div><p>W-17647069</p></div></div></td></tr><tr><td><div><div><p>This release includes security fixes.</p></div></div></td><td><div><div><p>W-17829729, W-17744569, W-17952645, W-17794265, W-17952607</p></div></div></td></tr><tr><td><div><div><p>The NodeAffinity configurations defined in the Kubernetes template are now consumed by the Runtime Fabric agent without the <strong>Enforce deploying replicas across nodes</strong> flag for Mule app deployments.</p></div></div></td><td><div><div><p>W-17778302</p></div></div></td></tr></tbody></table>

### Supported Kubernetes Versions

Runtime Fabric version 2.10.0 supports these Kubernetes versions:

- 1.31.x

- 1.30.x

- 1.29.x

- 1.28.x

## 2.9.2

**January 14, 2025**

### What’s New

- You can now
  [configure ingress with HTTP Route-Template Custom Resource](https://docs.mulesoft.com/runtime-fabric/latest/configure-ingress-http-resource)
  in Runtime Fabric.

  > [!NOTE] If you upgrade to Runtime Fabric version 2.9.2 and use the ingress template with port
  > number configuration other than 8081, then update the ingress template to either use port 8081
  > or use the recommended port name. For details on using port name, refer to
  > [Example Ingress Resource Templates](https://docs.mulesoft.com/runtime-fabric/latest/custom-ingress-configuration#kubernetes-ingress)

Currently, the `rtfctl backup` and `restore` commands aren’t supported for ingress with the HTTP
Route-Template Custom Resource.

After upgrading to Runtime Fabric agent 2.9.2, all new deployments and any redeployments will
include the following changes:

- The ingress naming convention is updated to `appName-uniqueIdentifier`. For example, for a test
  app, the resulting ingress name can be `test-dc844797c`.

- The app ingress resource is now managed by Helm as part of the Mule application deployment.

  - These dependencies are updated for
    [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

- agent version: `mulesoft/rtf-agent:2.9.2`

- coreAction: `mulesoft/rtf-core-actions:1.0.136`

- clusterOps: `mulesoft/rtf-cluster-ops:2.0.229`

- monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120`

- muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.23`

- appInit: `mulesoft/rtf-app-init:1.0.199`

- persistenceGateway: `mulesoft/rtf-object-store:1.0.222`

- resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.201`

- rtfDaemon: `mulesoft/rtf-daemon:2.0.129`

- Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.72`

  - These dependencies are updated for
    [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

- Ubi agent version: `mulesoft/rtf-agent-ubi:2.9.2`

- Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.136`

- Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.229`

- Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.23`

- Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.199`

- Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.222`

- Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.201`

- Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.129`

- Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.28`

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Outbound network tests now point to the correct control plane.</p></div></div></td><td><div><div><p>W-17129454</p></div></div></td></tr><tr><td><div><div><p>OpenShift infra nodes are no longer taken into account when calculating Runtime Fabric cluster capacity.</p></div></div></td><td><div><div><p>W-17407017</p></div></div></td></tr><tr><td><div><div><p>The deployment manifest file no longer returns duplicate entries for the <code>topologySpreadConstraints</code>.</p></div></div></td><td><div><div><p>W-16985683</p></div></div></td></tr></tbody></table>

### Supported Kubernetes Versions

Runtime Fabric version 2.9.2 supports these Kubernetes versions:

- 1.31.x

- 1.30.x

- 1.29.x

- 1.28.x

## 2.8.2

**October 21, 2024**

### What’s New

- Runtime Fabric now supports Kubernetes 1.30.

- Runtime Fabric no longer runs any Kubernetes CronJob. Now, the rtf-daemon component handles the
  certificate renewal.

- Helm-managed Runtime Fabric instances (rtf-daemon, agent, and resource-fetcher) are now FIPS 140-2
  compliant.

  To enable FIPS, set `fipsEnabled` to `true` in the Helm `values.yml` file.

  For more details, see:

- [Install Runtime Fabric with Helm: Optional Parameters](https://docs.mulesoft.com/runtime-fabric/latest/install-helm#optional-parameters)

- [Runtime Fabric Security Architecture](https://docs.mulesoft.com/runtime-fabric/latest/security-architecture#security-diagram)

- These dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.8.2`

  - coreAction: `mulesoft/rtf-core-actions:1.0.134`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.225`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.19`

  - appInit: `mulesoft/rtf-app-init:1.0.195`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.218`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.197`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.95`

  - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.62`

- These dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.8.2`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.134`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.225`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.19`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.195`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.218`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.197`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.95`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.28`

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When retrieving object store keys, the returned keys are no longer URL-encoded.</p></div></div></td><td><div><div><p>W-16487863</p></div></div></td></tr><tr><td><div><div><p>Parsing ingress templates without an HTTP path defined no longer returns an error.</p></div></div></td><td><div><div><p>W-16650398</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric upgrades no longer fail due to flex CRD installation.</p></div></div></td><td><div><div><p>W-16563430</p></div></div></td></tr></tbody></table>

### Supported Kubernetes Versions

Runtime Fabric version 2.8.2 supports these Kubernetes versions:

- 1.30.x

- 1.29.x

- 1.28.x

- 1.27.x

## 2.7.0

**August 15, 2024**

### What’s New

- For all OpenShift upgrades from versions 2.6.52 and earlier to versions 2.7.0 and later, manually
  increase the `rtfd` container resources to the desired values. See
  [Upgrade Pre-requisites](https://docs.mulesoft.com/runtime-fabric/latest/upgrade-pre-requisites).

- Runtime Fabric OpenShift operator is available in the stable release channel.

- More versions than just the last two OpenShift operator versions are now available to be
  installed.

- CPU limit for Runtime Fabric daemon has increased from 50m to 200m.

- The memory limit for Runtime Fabric daemon has increased from 250Mi to 300Mi.

- In large clusters, Runtime Fabric agent and Runtime Fabric daemon have shown approximately a 25%
  reduction in CPU usage and a 40% reduction in overall memory consumption. Additionally, the
  Runtime Fabric agent’s start-up time has improved by 20%, and deployment latency has been cut by
  around 6%. See [Scalability Benchmarks](https://docs.mulesoft.com/runtime-fabric/latest/rtf-scale) for guidance on
  large clusters.

- You can now use any Helm release name. However, `runtime-fabric` is still the default and
  recommended name.

- You can now override the creation of a new `ServiceAccount` for every Mule application deployment,
  by setting the `DISABLE_PER_APP_SA` variable in the `env` section of the Kubernetes template. See
  [Disable Per Application Service Account](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd#disable-service-account).

- The following dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.7.0`

  - coreAction: `mulesoft/rtf-core-actions:1.0.127`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.215`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.114`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.17`

  - appInit: `mulesoft/rtf-app-init:1.0.192`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.216`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.193`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.80`

  - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.48`

- The following dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.7.0`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.127`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.215`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.17`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.192`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.216`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.193`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.80`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.26`

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>An invalid <code>ephemeralStorageLimit</code> defined in the <code>KubernetesTemplate</code> now results in a more readable error message.</p></div></div></td><td><div><div><p>W-16441132</p></div></div></td></tr><tr><td><div><div><p>Increased nginx proxy defaults for worker processes/connections to allow more concurrent connections to take place. This can potentially improve throughput when a lot of configuration resolver requests are received at once.</p></div></div></td><td><div><div><p>W-13304547</p></div></div></td></tr><tr><td><div><div><p>Added explicit rate limit configuration to nginx proxy to avoid Denial-of-Service attacks.</p></div></div></td><td><div><div><p>W-15781441</p></div></div></td></tr></tbody></table>

### Kubernetes Supported Versions

This version of Runtime Fabric supports the following Kubernetes versions:

- 1.26.x

- 1.27.x

- 1.28.x

- 1.29.x

## 2.6.52

**June 7, 2024**

### What’s New

- Starting `rtfctl` version 1.0.70, if you use an rtf-agent version higher than 2.6.52, the `rtfctl`
  backup bundle doesn’t contain the Mule app deployments. The deployments are synced from the
  Runtime Manager UI at the time of restoration. Refer to
  [Backing up and restoring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-backup-restore).

- By default, console logging is disabled if your Mule app logs to at least one external source
  (such as Anypoint Monitoring or Splunk via a third-party Log4j appender). Using Anypoint
  Monitoring (with console logging disabled) can improve your Mule app’s performance by up to 40%.
  If you must use console logging, you can enable it by setting the `ENABLE_CONSOLE_LOG` variable to
  `"true"` in the `env` section of the Kubernetes template. For more information, refer to
  [Enable Console Logging](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd#enable-console-logging).

  > [!NOTE] For clusters that forward logs using `stdout`, there is potential impact on log
  > forwarding functionality. Work with your Kubernetes team to adjust log forwarding configurations
  > accordingly and ensure continuous log monitoring and collection.

- Review
  [Runtime Fabric Core Software Kubernetes Permissions](https://docs.mulesoft.com/runtime-fabric/latest/rtf-permissions)
  and
  [Mule App Deployments Kubernetes Permissions on Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/rtf-mule-app-permissions).

- Starting Runtime Fabric agent version 2.6.52, monitoringSidecar (otel) version is bound to Mule
  runtime versions. Refer to
  [Mule Runtime Patch Update Release Notes for Mule Apps on Runtime Fabric](https://docs.mulesoft.com/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes).

- You can now deploy
  [`SNAPSHOT` version assets](https://docs.mulesoft.com/exchange/to-publish-assets-maven#asset-lifecycle-state) to
  Runtime Fabric using the Mule Maven plugin without the need to increment your application’s
  version number manually. Refer to
  [Exchange Snapshot Assets](https://docs.mulesoft.com/runtime-fabric/latest/deploy-maven-4.x#exchange-snapshot-assets).
  Using Exchange snapshot assets in Anypoint Exchange during the development and testing phase, you
  can avoid incrementing your application’s version number for small changes. After your snapshot
  asset is overwritten in Anypoint Exchange, you can redeploy your `SNAPSHOT` version application to
  Runtime Fabric via the Mule Maven plugin to deploy the latest changes.

- The following dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.6.52`

  - coreAction: `mulesoft/rtf-core-actions:1.0.118`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.208`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.114`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.15`

  - appInit: `mulesoft/rtf-app-init:1.0.179`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.205`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.183`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.48`

  - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:1.2.152`

- The following dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.52`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.118`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.208`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.15`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.179`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.205`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.183`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.48`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.26`

### Kubernetes Supported Versions

This version of Runtime Fabric supports the following Kubernetes versions:

- 1.26.x

- 1.27.x

- 1.28.x

- 1.29.x

## 2.6.42

**May 13, 2024**

### What’s New

- You can now
  [enable trace data](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#enable-trace-data)
  collection for Mule apps. You can use the
  [Telemetry Exporter](https://docs.mulesoft.com/monitoring/telemetry-exporter) in Anypoint Monitoring to export traces
  to third-party observability and analytics apps.

- Refer to
  [Mule Runtime Patch Update Release Notes for Mule Apps on Runtime Fabric](https://docs.mulesoft.com/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes)
  going forward to check the latest Otel sidecar version.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>You can now view logs forwarded from Mule apps that have not restarted after upgrading to version 2.6.23 on non-Openshift self-managed platforms.</p></div></div></td><td><div><div><p>W-15666862</p></div></div></td></tr><tr><td><div><div><p>Mule apps no longer start with a warning regarding an invalid group ID.</p></div></div></td><td><div><div><p>W-15362056</p></div></div></td></tr></tbody></table>

- The following dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.6.42`

  - coreAction: `mulesoft/rtf-core-actions:1.0.116`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.205`

  - monitoringSidecar (otel): `mulesoft/dias-anypoint-monitoring-sidecar:2.0.45`

  - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.114`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.11`

  - appInit: `mulesoft/rtf-app-init:1.0.176`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.201`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.180`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.44`

  - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.148`

- The following dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.42`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.116`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.205`

  - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:2.0.45`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.11`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.176`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.201`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.180`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.44`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.25`

### Kubernetes Supported Versions

This version of Runtime Fabric supports the following Kubernetes versions:

- 1.25.x

- 1.26.x

- 1.27.x

- 1.28.x

## 2.6.23

**April 17, 2024**

### What’s New

- If you have a self-hosted container registry, you may encounter a no image found error during app
  restart or redeployment. Due to this, any redeployment or deployments using version 2.6.22 after
  May 15 will use the new 2.0.45 sidecar version. As a workaround, pull the image 2.0.45 to the
  local registry. Refer to
  [Synchronize Runtime Fabric Core Software Dependencies and Images to Your Local Registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry#synch-rtf).

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>For Openshift clusters, upgrade to Runtime Fabric version 2.6.23 to avoid noisy warning log messages in Runtime Fabric agent.</p></div></div></td><td><div><div><p>W-15532104</p></div></div></td></tr></tbody></table>

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Known Issue</th><th>Workaround</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Unable to view logs forwarded from Mule apps that have not restarted after upgrading to version 2.6.23 on non-Openshift self-managed platforms.</p></div></div></td><td><div><div><p>Do not upgrade to version 2.6.23 and wait for the next version release. If you already upgraded, refer to the <a href="https://help.salesforce.com/s/articleView?id=001859656&amp;type=1">Anypoint Monitoring Log Forwarder Pods (daemon set) stop sending logs after upgrade to RTF agent version 2.6.22 or 2.6.23</a> knowledge base article for potential workarounds.</p></div></div></td><td><div><div><p>W-15666862</p></div></div></td></tr></tbody></table>

- The following dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.6.23`

  - coreAction: `mulesoft/rtf-core-actions:1.0.113`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.181`

  - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:2.0.45`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.11`

  - appInit: `mulesoft/rtf-app-init:1.0.170`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.197`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.174`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.34`

  - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.100`

- The following dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.23`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.113`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.181`

  - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:2.0.45`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.11`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.170`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.197`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.174`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.34`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.20`

### Kubernetes Supported Versions

This version of Runtime Fabric supports the following Kubernetes versions:

- 1.25.x

- 1.26.x

- 1.27.x

- 1.28.x

## 2.6.22

**April 11, 2024**

### What’s New

- Starting Runtime Fabric version 2.6.22, you must configure new
  [Anypoint Monitoring endpoints](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#enable-anypoint-monitoring)
  for Runtime Fabric instance setup.

- Starting version 2.6.22 Anypoint Monitoring sidecar is only compatible with http-proxy instead of
  the monitoring SOCKS5 proxy. If you run Mule apps in a controlled environments, ensure you
  [configure an HTTP proxy for services in Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-proxy-self#configure-an-http-proxy-for-services-in-runtime-fabric).
  Note that if you have a self-hosted container registry, you may encounter no image found error
  during app restart or redeployment. Due to this, any redeployment or deployments using version
  2.6.22 after May 15 will use the new 2.0.45 sidecar version. As a workaround pull the image 2.0.45
  to the local registry. Refer to
  [Synchronize Runtime Fabric Core Software Dependencies and Images to Your Local Registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry#synch-rtf).

- Runtime Fabric now supports Horizontal Pod Autoscaling (HPA), refer to
  [Configuring Horizontal Pod Autoscaling (HPA) for Runtime Fabric Deployments](https://docs.mulesoft.com/runtime-fabric/latest/configure-horizontal-autoscaling)

To upgrade an already created Runtime Fabric in an old K8s cluster version, you must first upgrade
the agent to the new version, and then upgrade the cluster to use K8s.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The cluster health status box in the Runtime Manager user interface no longer displays more nodes than were actually live.</p></div></div></td><td><div><div><p>W-14374870</p></div></div></td></tr><tr><td><div><div><p>Persistence Gateway no more fails with the error `reached maximum value of sequence "items_id_seq".</p></div></div></td><td><div><div><p>W-14811114</p></div></div></td></tr><tr><td><div><div><p>Added timezone to the Mule-license expiry info which is displayed on the Runtime Fabric user interface.</p></div></div></td><td><div><div><p>W-15177341</p></div></div></td></tr></tbody></table>

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Known Issue</th><th>Workaround</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Unable to view logs forwarded from Mule apps that have not restarted after upgrading to version 2.6.22 on non-Openshift self-managed platforms.</p></div></div></td><td><div><div><p>Do not upgrade to version 2.6.22 and wait for the next version release. If you already upgraded, refer to the <a href="https://help.salesforce.com/s/articleView?id=001859656&amp;type=1">Anypoint Monitoring Log Forwarder Pods (daemon set) stop sending logs after upgrade to RTF agent version 2.6.22 or 2.6.23</a> knowledge base article for potential workarounds.</p></div></div></td><td><div><div><p>W-15666862</p></div></div></td></tr></tbody></table>

- The following dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.6.22`

  - coreAction: `mulesoft/rtf-core-actions:1.0.113`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.181`

  - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:2.0.34`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.11`

  - appInit: `mulesoft/rtf-app-init:1.0.170`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.197`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.174`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.34`

  - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.100`

- The following dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.22`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.113`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.181`

  - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:2.0.34`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.11`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.170`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.197`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.174`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.34`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.20`

### Kubernetes Supported Versions

This version of Runtime Fabric supports the following Kubernetes versions:

- 1.25.x

- 1.26.x

- 1.27.x

- 1.28.x

## 2.6.2

**March 5, 2024**

### What’s New

- Runtime Fabric now supports Kubernetes 1.28.

  To upgrade an already created Runtime Fabric in an old K8s cluster version, you must first upgrade
  the agent to the new version, and then upgrade the cluster to use K8s v1.28.

- MuleSoft now consolidates telemetry transport through a single sidecar per application replica.
  Review the resource allocation changes of Anypoint Monitoring agent that enables you to
  [monitor Mule apps deployed on Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#resource-and-permission-requirements-for-anypoint-monitoring-agent).

- Review how to
  [synchronize image dependencies to your local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry)
  using `helm` or `rtfctl`.

- Mule app deployments via the API with AM log forwarding `enabled` must have the Mule app
  deployment request `disableAmLogForwarding` set to `false`.

- Review
  [customize Mule app Kubernetes resources](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd) on
  how to customize `automountServiceAccountToken` using CRD.

- Review
  [downgrading Runtime Fabric Versions](https://docs.mulesoft.com/runtime-fabric/latest/downgrade-runtime-fabric).

- Starting with this version, there are changes to the registry endpoint validation. Previously, an
  empty authorization header was sent during the probe on the registry endpoint for network
  checking. Now, Runtime Fabric sends no authorization header at all. If you are using a private
  registry, you might find that your network checks fail on the registry endpoint.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>For OpenShift clusters, Mule app’s ingress now uses <code>openshift-default</code> as the <code>ingressClassName</code> when using <code>rtf-openshift</code> in the ingress template.</p></div></div></td><td><div><div><p>W-13840301</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric OpenShift route template now supports the default TLS-certificate.</p></div></div></td><td><div><div><p>W-14937104</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric BYOK ingress template with multi-hosts now propagates correctly the protocol to the Runtime Manager UI.</p></div></div></td><td><div><div><p>W-14687741</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric daemon no longer ignores Anypoint Monitoring proxy.</p></div></div></td><td><div><div><p>W-14785603</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric object store service now returns a structured response for errors.</p></div></div></td><td><div><div><p>W-14446241</p></div></div></td></tr><tr><td><div><div><p>This release includes security fixes.</p></div></div></td><td><div><div><p>W-14309677</p></div></div></td></tr><tr><td><div><div><p>Cluster IP service now works correctly with Runtime Fabrics installed in a custom namespace.</p></div></div></td><td><div><div><p>W-14828458</p></div></div></td></tr></tbody></table>

- The following dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:2.6.2`

  - coreAction: `mulesoft/rtf-core-actions:1.0.104`

  - clusterOps: `mulesoft/rtf-cluster-ops:2.0.176`

  - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:1.3.111`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.7`

  - appInit: `mulesoft/rtf-app-init:1.0.160`

  - persistenceGateway: `mulesoft/rtf-object-store:1.0.185`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.167`

  - rtfDaemon: `mulesoft/rtf-daemon:2.0.29`

  - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.100`

- The following dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.2`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.104`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.176`

  - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:1.3.111`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.7`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.3.111`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.185`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.167`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.29`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.20`

### Kubernetes Supported Versions

This version of Runtime Fabric supports the following Kubernetes versions:

- 1.25.x

- 1.26.x

- 1.27.x

- 1.28.x

## 2.5.0

**November 15, 2023**

### What’s New

- Runtime Fabric now supports Kubernetes 1.27.  
  To upgrade an already created Runtime Fabric in an old K8s cluster version, you must first upgrade
  the agent to the new version, and then upgrade the cluster to use K8s v1.27.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Runtime Fabric namespaced Kubernetes templates in authorized mode and handling of node affinity rules now work correctly.</p></div></div></td><td><div><div><p>W-14182584</p></div></div></td></tr><tr><td><div><div><p>The ingress template now uses OCP default certificate for TLS Runtime Manager details to show the URL as plain HTTP instead of HTTPS.</p></div></div></td><td><div><div><p>W-13750378</p></div></div></td></tr><tr><td><div><div><p>Runtime Fabric agent now recovers correctly after a network outage if proxy is enabled.</p></div></div></td><td><div><div><p>W-14308672</p></div></div></td></tr><tr><td><div><div><p>The ingress resource watcher no longer publishes the ingress template every hour resulting in the CPU spike at the ingress controller.</p></div></div></td><td><div><div><p>W-13588326</p></div></div></td></tr></tbody></table>

### Known Issues

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Known Issue</th><th>Workaround</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>For Runtime Fabric instances on OpenShift cluster, which are using <a href="https://docs.mulesoft.com/runtime-fabric/latest/authorized-namespaces">authorized namespaces</a>, additional ClusterRolebinding is required. If not provided <code>InvalidSemverException</code> occurs during the deployment of a Mule app.</p></div></div></td><td><div><div><p>Refer to <a href="https://help.salesforce.com/s/issue?id=a028c00000yEJY7">2.5.0 - Ingress creation failure (InvalidSemverException)</a> for details.</p></div></div></td><td><div><div><p>W-14668801</p></div></div></td></tr></tbody></table>

- The following dependencies are updated for
  [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry):

  - agent version: `mulesoft/rtf-agent:v2.5.0`

  - coreAction: `mulesoft/rtf-core-actions:v1.0.88`

  - clusterOps: `mulesoft/rtf-cluster-ops:v2.0.141`

  - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:v1.3.90`

  - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:v1.3.22`

  - appInit: `mulesoft/rtf-app-init:v1.0.141`

  - persistenceGateway: `mulesoft/rtf-object-store:v1.0.158`

  - resourceFetcher: `mulesoft/rtf-resource-fetcher:v1.0.151`

  - rtfDaemon: `mulesoft/rtf-daemon:v2.0.10`

  - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.87`

- The following dependencies are updated for
  [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift):

  - Ubi agent version: `mulesoft/rtf-agent-ubi:v2.5.0`

  - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:v1.0.88`

  - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:v2.0.141`

  - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:v1.3.90`

  - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:v1.3.22`

  - Ubi appInit: `mulesoft/rtf-app-init-ubi:v1.0.141`

  - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:v1.0.158`

  - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.151`

  - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:v2.0.10`

  - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:v0.3.17`

### Kubernetes Supported Versions

This version of Runtime Fabric supports the following Kubernetes versions:

- 1.24.x

- 1.25.x

- 1.26.x

- 1.27.x

## See Also

- [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl)

- [Known Issues](https://help.salesforce.com/s/issues)