When retrieving object store keys, the returned keys are no longer URL-encoded.
Anypoint Runtime Fabric 2.x.x Release Notes
The following are release notes for Runtime Fabric v2.x.x.
For the complete Runtime Fabric documentation, see Anypoint Runtime Fabric.
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:
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 |
Runtime Fabric support GA of 1.30 |
1.27 |
April 2023 |
November 2023 |
Runtime Fabric support GA of 1.31 |
1.28 |
August 2023 |
March 2024 |
Runtime Fabric support of 1.32 |
1.29 |
December 2023 |
June 2024 |
Runtime Fabric support of 1.33 |
1.30 |
May 2024 |
October 2024 |
Runtime Fabric support of 1.34 |
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
totrue
in the Helmvalues.yml
file.For more details, see:
-
These dependencies are updated for installing and managing Runtime Fabric with a 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:
-
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 monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar-ubi:1.3.120
-
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
Issue Resolution | ID |
---|---|
W-16487863 |
|
Parsing ingress templates without an HTTP path defined no longer returns an error. |
W-16650398 |
Runtime Fabric upgrades no longer fail due to flex CRD installation. |
W-16563430 |
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. -
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 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 theDISABLE_PER_APP_SA
variable in theenv
section of the Kubernetes template. See Disable Per Application Service Account. -
The following dependencies are updated for installing and managing Runtime Fabric with a 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:
-
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 monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar-ubi:1.3.114
-
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
Issue Resolution | ID |
---|---|
An invalid |
W-16441132 |
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. |
W-13304547 |
Added explicit rate limit configuration to nginx proxy to avoid Denial-of-Service attacks. |
W-15781441 |
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, thertfctl
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. -
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 theenv
section of the Kubernetes template. For more information, refer to Enable Console Logging.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 and Mule App Deployments Kubernetes Permissions on Runtime Fabric.
-
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.
-
You can now deploy
SNAPSHOT
version assets to Runtime Fabric using the Mule Maven plugin without the need to increment your application’s version number manually. Refer to 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 yourSNAPSHOT
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:
-
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:
-
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 monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar-ubi:1.3.114
-
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
-
2.6.42
May 13, 2024
What’s New
-
You can now enable trace data collection for Mule apps. You can use the 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 going forward to check the latest Otel sidecar version.
Fixed Issues
Issue Resolution | ID |
---|---|
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. |
W-15666862 |
Mule apps no longer start with a warning regarding an invalid group ID. |
W-15362056 |
-
The following dependencies are updated for installing and managing Runtime Fabric with a 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:
-
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
-
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.
Fixed Issues
Issue Resolution | ID |
---|---|
For Openshift clusters, upgrade to Runtime Fabric version 2.6.23 to avoid noisy warning log messages in Runtime Fabric agent. |
W-15532104 |
Known Issue | Workaround | ID |
---|---|---|
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. |
Do not upgrade to version 2.6.23 and wait for the next version release. If you already upgraded, refer to the Anypoint Monitoring Log Forwarder Pods (daemon set) stop sending logs after upgrade to RTF agent version 2.6.22 or 2.6.23 knowledge base article for potential workarounds. |
W-15666862 |
-
The following dependencies are updated for installing and managing Runtime Fabric with a 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:
-
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
-
2.6.22
April 11, 2024
What’s New
-
Starting Runtime Fabric version 2.6.22, you must configure new Anypoint Monitoring endpoints 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. 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.
-
Runtime Fabric now supports Horizontal Pod Autoscaling (HPA), refer to Configuring Horizontal Pod Autoscaling (HPA) for Runtime Fabric Deployments
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
Issue Resolution | ID |
---|---|
The cluster health status box in the Runtime Manager user interface no longer displays more nodes than were actually live. |
W-14374870 |
Persistence Gateway no more fails with the error `reached maximum value of sequence "items_id_seq". |
W-14811114 |
Added timezone to the Mule-license expiry info which is displayed on the Runtime Fabric user interface. |
W-15177341 |
Known Issue | Workaround | ID |
---|---|---|
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. |
Do not upgrade to version 2.6.22 and wait for the next version release. If you already upgraded, refer to the Anypoint Monitoring Log Forwarder Pods (daemon set) stop sending logs after upgrade to RTF agent version 2.6.22 or 2.6.23 knowledge base article for potential workarounds. |
W-15666862 |
-
The following dependencies are updated for installing and managing Runtime Fabric with a 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:
-
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
-
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.
-
Review how to synchronize image dependencies to your local registry using
helm
orrtfctl
. -
Mule app deployments via the API with AM log forwarding
enabled
must have the Mule app deployment requestdisableAmLogForwarding
set tofalse
. -
Review customize Mule app Kubernetes resources on how to customize
automountServiceAccountToken
using CRD. -
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
Issue Resolution | ID |
---|---|
For OpenShift clusters, Mule app’s ingress now uses |
W-13840301 |
Runtime Fabric OpenShift route template now supports the default TLS-certificate. |
W-14937104 |
Runtime Fabric BYOK ingress template with multi-hosts now propagates correctly the protocol to the Runtime Manager UI. |
W-14687741 |
Runtime Fabric daemon no longer ignores Anypoint Monitoring proxy. |
W-14785603 |
Runtime Fabric object store service now returns a structured response for errors. |
W-14446241 |
This release includes security fixes. |
W-14309677 |
Cluster IP service now works correctly with Runtime Fabrics installed in a custom namespace. |
W-14828458 |
-
The following dependencies are updated for installing and managing Runtime Fabric with a 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:
-
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
-
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
Issue Resolution | ID |
---|---|
Runtime Fabric namespaced Kubernetes templates in authorized mode and handling of node affinity rules now work correctly. |
W-14182584 |
The ingress template now uses OCP default certificate for TLS Runtime Manager details to show the URL as plain HTTP instead of HTTPS. |
W-13750378 |
Runtime Fabric agent now recovers correctly after a network outage if proxy is enabled. |
W-14308672 |
The ingress resource watcher no longer publishes the ingress template every hour resulting in the CPU spike at the ingress controller. |
W-13588326 |
Known Issues
Known Issue | Workaround | ID |
---|---|---|
For Runtime Fabric instances on OpenShift cluster, which are using authorized namespaces, additional ClusterRolebinding is required. If not provided |
Refer to 2.5.0 - Ingress creation failure (InvalidSemverException) for details. |
W-14668801 |
-
The following dependencies are updated for installing and managing Runtime Fabric with a 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:
-
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
-
2.4.45
September 25, 2023
What’s New
-
Runtime Fabric now supports Alibaba Cloud Container Service for Kubernetes (ACK), VMware Tanzu Kubernetes Grid, and Rancher Kubernetes Engine (RKE).
Fixed Issues
Issue Resolution | ID |
---|---|
The AM Daemonset can now be turned off correctly. |
W-13667527 |
For OpenShift clusters Runtime Fabric API now shows the controller and worker nodes correctly. |
W-13756093 |
Mule apps on OpenShift clusters when redeployed after upgrading to Runtime Fabric 2.4.0 no longer need to stop and start for Mule app recovery. |
W-13926387 |
-
The following dependencies are updated for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:v2.4.45
-
coreAction:
mulesoft/rtf-core-actions:v1.0.77
-
clusterOps:
mulesoft/rtf-cluster-ops:v2.0.121
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.90
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.3.18
-
appInit:
mulesoft/rtf-app-init:v1.0.128
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.147
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.139
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.166
-
Base Image Nginx:
mulesoft/base-image-nginx-1.21.6:v1.2.63
-
-
The following dependencies are updated for installing Runtime Fabric as a Kubernetes (K8s) Operator:
-
Ubi agent version:
mulesoft/rtf-agent-ubi:v2.4.45
-
Ubi coreAction:
mulesoft/rtf-core-actions-ubi:v1.0.77
-
Ubi clusterOps:
mulesoft/rtf-cluster-ops-ubi:v2.0.121
-
Ubi monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar-ubi:v1.3.90
-
Ubi muleClusterIpService:
mulesoft/rtf-mule-clusterip-service-ubi:v1.3.18
-
Ubi appInit:
mulesoft/rtf-app-init-ubi:v1.0.128
-
Ubi persistenceGateway:
mulesoft/rtf-object-store-ubi:v1.0.147
-
Ubi resourceFetcher:
mulesoft/rtf-resource-fetcher-ubi:v1.0.139
-
Ubi rtfDaemon:
mulesoft/rtf-daemon-ubi:v1.0.166
-
Ubi Base Nginx:
mulesoft/rtf-ubi-base-nginx:v0.3.14
-
2.4.0
August 7th, 2023
What’s New
-
For Runtime Fabric agent installed on OpenShift, any new Mule app deployment must use a Mule runtime image built on August 8, 2023, or later.
-
Review new Secure Runtime Fabric documentation.
-
Review new Anypoint Runtime Fabric Security Architecture documentation.
-
Review new Kubernetes Hardening guide documentation.
-
-
You can now customize your Mule app Kubernetes resources through the custom resource
kubernetestemplates.rtf.mulesoft.com
template. See Customize Mule App Using Kubernetes Resources (CRD). -
You can now deploy Mule apps to Runtime Fabric using Anypoint CLI. See Deploying and Managing Mule Apps from the CLI.
-
You can now deploy apps with sizes up to 350 MB to Runtime Fabric targets.
-
The namespace in which your Runtime Fabric has been installed is now displayed on the fabric details page of the Anypoint Runtime Manager UI.
-
The following dependencies are updated for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:v2.4.0
-
coreAction:
mulesoft/rtf-core-actions:v1.0.71
-
clusterOps:
mulesoft/rtf-cluster-ops:v2.0.106
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.77
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.3.13
-
appInit:
mulesoft/rtf-app-init:v1.0.116
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.135
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.130
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.152
-
Base Image Nginx:
mulesoft/base-image-nginx-1.21.6:v1.2.45
-
-
The following dependencies are updated for installing Runtime Fabric as a Kubernetes (K8s) Operator:
-
Ubi agent version:
mulesoft/rtf-agent-ubi:v2.4.0
-
Ubi coreAction:
mulesoft/rtf-core-actions-ubi:v1.0.71
-
Ubi clusterOps:
mulesoft/rtf-cluster-ops-ubi:v2.0.11
-
Ubi monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar-ubi:v1.3.77
-
Ubi muleClusterIpService:
mulesoft/rtf-mule-clusterip-service-ubi:v1.3.13
-
Ubi appInit:
mulesoft/rtf-app-init-ubi:v1.0.116
-
Ubi persistenceGateway:
mulesoft/rtf-object-store-ubi:v1.0.135
-
Ubi resourceFetcher:
mulesoft/rtf-resource-fetcher-ubi:v1.0.130
-
Ubi rtfDaemon:
mulesoft/rtf-daemon-ubi:v1.0.152
-
Ubi Base Nginx:
mulesoft/rtf-ubi-base-nginx:v0.3.9
-
Fixed Issues
Issue Resolution | ID |
---|---|
Persistence Gateway no longer makes object stores overwrite key values when it is expected to fail. Mule apps that use the Object Store Connector |
W-13592329 |
The |
W-13565860 |
Runtime Fabric OpenShift no longer creates a new service account for every deployment. |
W-13305043 |
Clustered apps now run correctly on a multi-instance or custom agent namespace setup. |
W-13740421 |
Runtime Fabric no longer shows the incorrect maximum memory for node. |
W-13123041 |
Kubernetes Supported Versions
This version of Runtime Fabric supports the following Kubernetes versions:
-
1.23.x
-
1.24.x
-
1.25.x
-
1.26.x
Known Issues
Known Issue | Workaround | ID |
---|---|---|
Mule apps deployed to Runtime Fabric on OpenShift must be upgraded to the latest Mule runtime engine patches versions available 4.4.0, 4.3.0, or 3.9.x, before upgrading RTF agent to 2.4.0. Applications will continue running successfully after upgrading, although re-deployments of Mule apps deployed before RTF agent upgrade will run into issues and display unable to validate against any security context constraint error message. |
Stop and re-start your Mule app. To downgrade RTF agent from 2.4.0 to 2.3.34, see Install old RTF operators in OCP platform or contact MuleSoft Support team. New Mule app deployments on RTF 2.4.0 do not have any impact. |
W-13926387 |
2.3.34
June 15th, 2023
What’s New
-
Runtime Fabric now supports Kubernetes version 1.26.
-
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.26.
-
-
Runtime Fabric OpenShift operator: For runtime-fabric-operator-controller-manager pod manager container’s memory limit is increased to 2048 Mi.
-
GKE K8s 1.26 is compatible only with Mule runtime engine patches June 6, 2023 and later.
-
The following dependencies are updated for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:v2.3.34
-
coreAction:
mulesoft/rtf-core-actions:v1.0.67
-
clusterOps:
mulesoft/rtf-cluster-ops:v2.0.88
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.77
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.3.10
-
appInit:
mulesoft/rtf-app-init:v1.0.106
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.126
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.120
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.132
-
Base Image Nginx:
mulesoft/base-image-nginx-1.21.6:v1.2.31
-
-
The following dependencies are updated for installing Runtime Fabric as a Kubernetes (K8s) Operator:
-
Ubi agent version:
mulesoft/rtf-agent-ubi:v2.3.34
-
Ubi clusterOps:
mulesoft/rtf-cluster-ops-ubi:v2.0.88
-
Ubi monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar-ubi:v1.3.77
-
Ubi muleClusterIpService:
mulesoft/rtf-mule-clusterip-service-ubi:v1.3.10
-
Ubi appInit:
mulesoft/rtf-app-init-ubi:v1.0.106
-
Ubi persistenceGateway:
mulesoft/rtf-object-store-ubi:v1.0.126
-
Ubi resourceFetcher:
mulesoft/rtf-resource-fetcher-ubi:v1.0.120
-
Ubi rtfDaemon:
mulesoft/rtf-daemon-ubi:v1.0.132
-
Ubi Base Nginx:
mulesoft/rtf-ubi-base-nginx:v0.3.9
-
Fixed Issues
Issue Resolution | ID |
---|---|
This release includes security fixes. |
W-13460997, W-13520411, W-13260915, W-13520416 |
AM sidecar memory is increased to prevent OOM (Out of memory), when sidecar is used for log forwarding. |
W-13506365 |
2.3.1
May 18th, 2023
What’s New
-
Runtime Fabric now supports Kubernetes version 1.25.
-
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.25.
-
Due to AKS 1.25 cluster performance memory-consumption issues, Runtime Fabric and Mule app deployments could require more resources than expected. K8s 1.25 is compatible only with Mule runtime engine patches June 6, 2023 and later.
-
-
Runtime Fabric now supports Amazon Elastic Kubernetes Service Anywhere (Amazon EKS-A).
-
Runtime Fabric now enables you to get the Mule License key expiry date. Refer to the get license expiry date documentation.
-
Review new Kubernetes (K8s) Best Practices for Runtime Fabric
-
Review Runtime Fabric scalability benchmarks documentation to understand scale limits for improvement of 8000 application deployments.
-
Runtime Fabric applications now support Anypoint app scheduler. Refer to the managing app schedules documentation.
-
The following dependencies are updated for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:v2.3.1
-
coreAction:
mulesoft/rtf-core-actions:v1.0.60
-
clusterOps:
mulesoft/rtf-cluster-ops:v2.0.61
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.74
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.3.5
-
appInit:
mulesoft/rtf-app-init:v1.0.91
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.112
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.107
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.125
-
Base Image Nginx:
mulesoft/base-image-nginx-1.21.6:v1.2.25
-
-
The following dependencies are updated for installing Runtime Fabric as a Kubernetes (K8s) Operator:
-
Ubi agent version:
mulesoft/rtf-agent-ubi:v2.3.1
-
Ubi clusterOps:
mulesoft/rtf-cluster-ops-ubi:v2.0.61
-
Ubi monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar-ubi:v1.3.74
-
Ubi muleClusterIpService:
mulesoft/rtf-mule-clusterip-service-ubi:v1.3.5
-
Ubi appInit:
mulesoft/rtf-app-init-ubi:v1.0.91
-
Ubi persistenceGateway:
mulesoft/rtf-object-store-ubi:v1.0.112
-
Ubi resourceFetcher:
mulesoft/rtf-resource-fetcher-ubi:v1.0.107
-
Ubi rtfDaemon:
mulesoft/rtf-daemon-ubi:v1.0.125
-
Ubi Base Nginx:
mulesoft/rtf-ubi-base-nginx:v0.3.9
-
Fixed Issues
Issue Resolution | ID |
---|---|
Runtime Fabric now supports enabling and disabling NodeWatcher and RateLimit deployments with Helm values. |
W-12469384 |
PSPs are no longer supported. |
W-12213515 |
Added new security fixes. |
W-12692341 |
2.2.5
April 11, 2023
What’s New
-
Runtime Fabric now supports multiple instances on a single cluster. Refer to the Installing Multiple Instances of Runtime Fabric on a Single Cluster documentation.
-
Updated dependencies for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:v2.2.5
-
coreAction:
mulesoft/rtf-core-actions:v1.0.55
-
clusterOps:
mulesoft/rtf-cluster-ops:v2.0.45
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.70
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.3.1
-
appInit:
mulesoft/rtf-app-init:v1.0.87
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.108
-
nginx:
mulesoft/base-image-nginx-1.21.6:v1.2.23
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.103
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.98
-
Fixed Issues
Issue Resolution | ID |
---|---|
Improved cluster status by reducing wait time to view agent status on the UI after installing or upgrading. |
W-12608467 |
Runtime Fabric now spreads Mule app replicas correctly across different nodes and availability zones. Redeploy the application to Runtime Fabric to spread the replicas to the nodes running in the zone |
W-11983686 |
A Runtime Fabric jar update during deployment now updates the generation pod label and does not leave the pods in pending state on small clusters. |
W-12190565 |
2.1.30
January 23, 2023
What’s New
-
The use of custom Log4j appenders is now disabled by default in Runtime Fabric. See Integrating with Your Logging System Using Log4j for more information on enabling and using Log4j appenders.
-
This release adds support for Red Hat OpenShift Routes in Runtime Fabric. For information on configuring routes, see Configuring Red Hat OpenShift Routes in Runtime Fabric.
-
This release adds support for Kubernetes version 1.24.x for Runtime Fabric on Self-Managed Kubernetes.
-
Updated dependencies for installing and managing Runtime Fabric with a local registry
-
agent version:
mulesoft/rtf-agent:v2.1.30
-
coreAction:
mulesoft/rtf-core-actions:v1.0.46
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.62
-
clusterOps:
mulesoft/rtf-cluster-ops:v2.0.6
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.2.74
-
appInit:
mulesoft/rtf-app-init:v1.0.75
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.101
-
nginx:
mulesoft/base-image-nginx-1.21.1:v1.2.13
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.90
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.76
-
Fixed Issues
Issue Resolution | ID |
---|---|
This release includes several security fixes. |
W-12082836 |
Agent disconnect issue no longer occurs after upgrading to the latest version. |
W-12042544 |
Using rtfctl to back up or restore a cluster without Persistence Gateway resources now works correctly. |
W-11987155 |
The core pricing metrics error |
W-13136267 |
Monitoring sidecar no longer produces error logs. |
W-11559681 |
2.1.0
November 8, 2022
What’s New
The Runtime Fabric Red Hat OpenShift operator v2.1.0 was released on December 16, 2022. |
-
You can now protect application property values of applications deployed to Runtime Fabric by displaying the property name, but not its value, in Anypoint Runtime Manager. See Protect Application Property Values in Runtime Fabric for more information.
-
You can now use a Log4j appender to integrate your logging system with applications deployed to Runtime Fabric. See Integrating with Your Logging System Using Log4j for more information.
-
You can now dynamically apply log levels when deploying apps on Runtime Fabric.
-
This release supports Kubernetes version 1.23.x on GKE and EKS.
-
This release includes security fixes.
-
Updated dependencies for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:v2.1.0
-
coreAction:
mulesoft/rtf-core-actions:v1.0.42
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.40
-
clusterOps:
mulesoft/rtf-cluster-ops:v1.1.91
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.2.74
-
appInit:
mulesoft/rtf-app-init:v1.0.71
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.95
-
nginx:
mulesoft/base-image-nginx-1.21.1:v1.2.8
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.85
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.69
-
Fixed Issues
Issue Resolution | ID |
---|---|
This release includes several security fixes. |
|
Persistence gateway pod replicas are no longer incorrectly scheduled on the same node. |
W-10867273 |
The Runtime Fabric agent container no longer restarts with an out of memory (OOM) error. |
W-11558741 |
Known Issues
Known Issue | Workaround | ID |
---|---|---|
This upgrade includes a runtime log format change which may impact Anypoint Monitoring log forwarding. |
Refer to the MuleSoft Knowledge Base for a workaround. |
W-12082202 |
2.0.0
September 13, 2022
What’s New
-
You can now deploy Runtime Fabric on Red Hat OpenShift. Runtime Fabric supports the following deployment options:
-
Red Hat OpenShift Service on AWS
-
Microsoft Azure Red Hat OpenShift
-
Red Hat OpenShift Dedicated
-
Red Hat OpenShift on IBM Cloud
-
Self-managed Red Hat OpenShift editions (Performance Plus, OCP, Kubernetes engine)
Runtime Fabric supports Red Hat OpenShift versions 4.6 to 4.10.
See the installation instructions to get started.
-
-
This release adds support for authorized namespaces on Runtime Fabric. Authorized namespaces enable you to deploy Runtime Fabric alongside other services in a Kubernetes cluster. See Configuring Authorized Namespaces in Runtime Fabric for more information.
-
Updated dependencies for installing and managing Runtime Fabric with a local registry:
-
agent version:
mulesoft/rtf-agent:v2.0.0
-
coreAction:
mulesoft/rtf-core-actions:v1.0.38
-
monitoringSidecar:
mulesoft/dias-anypoint-monitoring-sidecar:v1.3.36
-
clusterOps:
mulesoft/rtf-cluster-ops:v1.1.77
-
muleClusterIpService:
mulesoft/rtf-mule-clusterip-service:v1.2.71
-
appInit:
mulesoft/rtf-app-init:v1.0.66
-
persistenceGateway:
mulesoft/rtf-object-store:v1.0.85
-
nginx:
mulesoft/base-image-nginx-1.21.1:v1.1.38
-
resourceFetcher:
mulesoft/rtf-resource-fetcher:v1.0.78
-
rtfDaemon:
mulesoft/rtf-daemon:v1.0.66
-
Fixed Issues
Description | Issue |
---|---|
This release includes security fixes for the several Runtime Fabric services: rtfd, clusterip-service, resource cache, and rtf-agent. |
N/A |
Runtime Fabric no longer issues a |
W-11727821 |
Persistence Gateway now correctly masks all sensitive data in logs. |
W-11572282 |