Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerThe following are release notes for Runtime Fabric v1.x.x.
The latest downloadable package versions are displayed in the Runtime Fabric downloads page, located in Anypoint Runtime Manager in the Runtime Fabrics tab. A link to each package’s release notes is provided.
For additional information on cluster-level component (installer package) upgrades, refer to Anypoint Runtime Fabric Installer Release Notes. Make sure to perform a cluster-level component upgrade if a new version of the installer package is available. Refer to Upgrade Runtime Fabric for more information.
Refer to the Anypoint Security Edge Release Notes for updates regarding the internal load balancer.
Complete Runtime Fabric documentation is available at Anypoint Runtime Fabric documentation.
Starting September 2022, agent releases for Runtime Fabric appliance distributions will continue on the v1.x.x line. Runtime Fabric agent releases on the v2.0.0 line apply only to partner platforms (both Kubernetes and VMs/Bare Metal). |
Runtime Fabric agent 1.13.112 and later should only be used with (rtf-installer) versions 2.0.1661808686-2ff0e92 or later. |
June 30, 2023
Issue Resolution | ID |
---|---|
This release includes several security fixes. |
W-12692341 |
The Applications dashboard now automatically picks up a series of values and updates the dashboard view correctly. |
W-12975095 |
January 23, 2023
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 includes security fixes.
Updated dependencies for installing and managing Runtime Fabric with a local registry:
agent version: mulesoft/rtf-agent:v1.13.112
coreAction: mulesoft/rtf-core-actions:v1.0.48
monitoringSidecar: mulesoft/dias-anypoint-monitoring-sidecar:v1.3.62
clusterOps: mulesoft/rtf-cluster-ops:v1.2.5
muleClusterIpService: mulesoft/rtf-mule-clusterip-service:v1.2.74
appInit: mulesoft/rtf-app-init:v1.0.76
persistenceGateway: mulesoft/rtf-object-store:v1.0.102
nginx: mulesoft/base-image-nginx-1.21.1:v1.2.15
resourceFetcher: mulesoft/rtf-resource-fetcher:v1.0.92
rtfDaemon: mulesoft/rtf-daemon:v1.0.76
Issue Resolution | ID |
---|---|
This release contains security fixes. |
W-12082836 |
Grafana dashboards no longer show inaccurate data for application graphs. |
W-11431389 |
Agent disconnect issue no longer occurs after upgrading to the latest version. |
W-12042544 |
Edge in Runtime Fabric gravity appliance now initializes in http-only mode. |
W-12101525 |
The core pricing metrics error |
W-13136267 |
Monitoring sidecar no longer produces error logs. |
W-11559681 |
November 17, 2022
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 upgrades Fluent Bit to version 1.2.83 for external log forwarding.
This release includes security fixes.
Updated dependencies for installing and managing Runtime Fabric with a local registry:
agent version: mulesoft/rtf-agent:v1.13.91
coreAction: mulesoft/rtf-core-actions:v1.0.44
monitoringSidecar: mulesoft/dias-anypoint-monitoring-sidecar:v1.3.40
clusterOps: mulesoft/rtf-cluster-ops:v1.2.2
muleClusterIpService: mulesoft/rtf-mule-clusterip-service:v1.2.75
appInit: mulesoft/rtf-app-init:v1.0.73
persistenceGateway: mulesoft/rtf-object-store:v1.0.98
nginx: mulesoft/base-image-nginx-1.21.1:v1.2.9
resourceFetcher: mulesoft/rtf-resource-fetcher:v1.0.88
rtfDaemon: mulesoft/rtf-daemon:v1.0.70
Description | Issue |
---|---|
This release contains a security fix. |
W-12045345 |
The Runtime Fabric agent no longer reports an OOM Killer process. |
W-11558741 |
Persistence gateway pod replicas are no longer incorrectly scheduled on the same node. |
W-10867273 |
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 |
August 3, 2022
This release adds supports for Kubernetes version 1.23 on Microsoft Azure Kubernetes Service (AKS).
This release upgrades Fluent Bit to version 1.8.14 for external log forwarding.
Reported security vulnerabilities are now fixed.
Updated dependencies for installing and managing Runtime Fabric with a local registry:
agent version: mulesoft/rtf-agent:v1.13.54
coreAction: mulesoft/rtf-core-actions:v1.0.30
monitoringSidecar: mulesoft/dias-anypoint-monitoring-sidecar:v1.3.26
clusterOps: mulesoft/rtf-cluster-ops:v1.1.63
muleClusterIpService: mulesoft/rtf-mule-clusterip-service:v1.2.61
appInit: mulesoft/rtf-app-init:v1.0.51
persistenceGateway: mulesoft/rtf-object-store:v1.0.74
nginx: mulesoft/base-image-nginx-1.21.1:v1.1.37
resourceFetcher: mulesoft/rtf-resource-fetcher:v1.0.71
rtfDaemon: mulesoft/rtf-daemon:v1.0.51
Description | Issue |
---|---|
The Runtime Fabric agent no longer restarts after an upgrade because of a WebSocket connection failure. |
W-11217136 |
Runtime Fabric services running in EKS clusters now refresh service tokens as expected. |
W-11188620 |
This release contains security fixes for Runtime Fabric components. |
W-11302288 |
June 2, 2022
Updated dependencies for installing and managing Runtime Fabric with a local registry:
agent version: mulesoft/rtf-agent:v1.13.6
appInit: mulesoft/rtf-app-init:v1.0.51
muleClusterIpService: mulesoft/rtf-mule-clusterip-service:v1.2.49
resourceFetcher: mulesoft/rtf-resource-fetcher:v1.0.59
nginx: mulesoft/base-image-nginx-1.21.1:v1.1.29
monitoringSidecar: mulesoft/dias-anypoint-monitoring-sidecar:v1.3.20
clusterOps: mulesoft/rtf-cluster-ops:v1.1.48
coreAction: mulesoft/rtf-core-actions:v1.0.21
persistenceGateway: mulesoft/rtf-object-store:v1.0.61
rtfDaemon: mulesoft/rtf-daemon:v1.0.29
Description | Issue |
---|---|
Nodes no longer show incorrect CPU values after an upgrade to 1.13.6 or later. |
W-11227257 |
May 24, 2022
You can now use Helm to install and upgrade Runtime Fabric on Self-Managed Kubernetes. Refer to Installing Runtime Fabric on Self-Managed Kubernetes Using Helm for instructions.
Note that Helm upgrades are not available for existing installations that used the rtfctl
command line tool.
This release adds support for Kubernetes version 1.22.x for Runtime Fabric on Self-Managed Kubernetes. This Kubernetes version removes several deprecated APIs. See Kubernetes Support for a full list of supported Kubernetes versions.
Updated dependencies for installing and managing Runtime Fabric with a local registry:
agent version: mulesoft/rtf-agent:v1.13.0
appInit: mulesoft/rtf-app-init:v1.0.51
muleClusterIpService: mulesoft/rtf-mule-clusterip-service:v1.2.49
resourceFetcher: mulesoft/rtf-resource-fetcher:v1.0.59
nginx: mulesoft/base-image-nginx-1.21.1:v1.1.29
monitoringSidecar: mulesoft/dias-anypoint-monitoring-sidecar:v1.3.20
clusterOps: mulesoft/rtf-cluster-ops:v1.1.48
coreAction: mulesoft/rtf-core-actions:v1.0.21
persistenceGateway: mulesoft/rtf-object-store:v1.0.61
rtfDaemon: mulesoft/rtf-daemon:v1.0.29
Description | Issue |
---|---|
The |
W-10760181 |
This release corrects an issue in which the control plane reported a mismatch in agent versions. |
W-10985884 |
This release contains security fixes for all Runtime Fabric components. |
N/A |
This release adds TCP keep-alive processing to ingress inbound connections. |
W-10818442 |
Anypoint Security Edge logs are now written to both file and stdout. |
W-11037800 |
Anypoint Security Edge logs are now rotated. |
W-11037810 |
Known Issue | Workaround | ID |
---|---|---|
If you plan to rollback to a version earlier than 1.13.0, and you have Anypoint Monitoring log forwarder enabled, you must disable it before you trigger the rollback. You can re-enable it after the rollback completes. |
N/A |
N/A |
March 30, 2022
Custom ingress for Runtime Fabric on Self-Managed Kubernetes now includes the unique-id
placeholder. Use this placeholder to create unique application URLs, for example, if you want to deploy two applications with the same name from different business groups.
Updated dependencies for installing and managing Runtime Fabric with a local registry:
appInit: mulesoft/rtf-app-init:v1.0.37
muleClusterIpService: mulesoft/rtf-mule-clusterip-service:v1.2.40
resourceFetcher: mulesoft/rtf-resource-fetcher:v1.0.48
nginx: mulesoft/base-image-nginx-1.21.1:v1.1.17
monitoringSidecar: mulesoft/dias-anypoint-monitoring-sidecar:v1.3.18
clusterOps: mulesoft/rtf-cluster-ops:v1.1.33
coreAction: mulesoft/rtf-core-actions:v1.0.16
persistenceGateway: mulesoft/rtf-object-store:v1.0.51
rtfDaemon: mulesoft/rtf-daemon:v1.0.16
Description | Issues |
---|---|
The external log forwarder no longer raises |
SE-22892 |
Subsequent requests no longer trigger the external log forwarder to create or delete deployments for the daemonset. |
W-10883503 |
The Runtime Fabric rtfd container no longer crashes with a |
W-10799741 |
Additionally, this release includes fixes for the following potential security vulnerabilities:
CVE-2022-25236
CVE-2022-25235
CVE-2022-24407
CVE-2022-0778
February 22, 2022
This release adds support for Kubernetes version 1.21.3, or later patch versions on 1.21.x, for Runtime Fabric on Self-Managed Kubernetes.
Runtime Fabric now includes a view-only permission. You don’t need to upgrade the agent to see this change.
When you enable or disable log forwarding, Runtime Manager now indicates that an agent restart is in progress. Additionally, when the restart is in progress, you can’t again enable or disable log forwarding.
When you deploy applications on Runtime Fabric on VMs / Bare Metal, ingress is now enabled by default. See Configure a Public Endpoint for the Application for VMs/Bare Metal for instructions to disable ingress if required.
You can now create your own namespaces for application deployments. See Creating Namespaces for Application Deployments for instructions.
Using Runtime Fabric on Self-Managed Kubernetes 1.12 and later, you can set up a local registry to pull and store the necessary Docker images for installing and managing Runtime Fabric. See Using a Local Registry with Runtime Fabric on Self-Managed Kubernetes.
Setting up a local registry requires these dependencies:
appInit: mulesoft/rtf-app-init:v1.0.37
muleClusterIpService: mulesoft/rtf-mule-clusterip-service:v1.2.37
resourceFetcher: mulesoft/rtf-resource-fetcher:v1.0.48
nginx: mulesoft/base-image-nginx-1.21.1:v1.1.11
monitoringSidecar: mulesoft/dias-anypoint-monitoring-sidecar:v1.3.18
clusterOps: mulesoft/rtf-cluster-ops:v1.1.28
coreAction: mulesoft/rtf-core-actions:v1.0.11
persistenceGateway: mulesoft/rtf-object-store:v1.0.49
rtfDaemon: mulesoft/rtf-daemon:v1.0.7
Description | Issues |
---|---|
When you delete applications, Runtime Fabric now removes ingress resources associated with them. |
SE-24146 |
Persistence Gateway no longer throws a 404 error if url-encoded characters are present in the request path. |
SE-24424 |
The error |
SE-23770 |
Runtime Fabric ingress nodes now correctly register all deployed APIs. |
SE-24285 |
The ingress controller for Runtime Fabric on VMs / Bare Metal contains several improvements. |
RTFC-1316, RTFC-1325, RTFC-1326, W-10647749 |
Anypoint Monitoring metrics and logs are populated as expected after an update to the Monitoring agent certificate. |
N/A |
Known Issue | Workaround | ID |
---|---|---|
When Runtime Fabric version 1.12 is running with a proxy, the |
Refer to the MuleSoft Knowledge Base for a workaround. |
W-10799741 |
December 17, 2021
This release adds stability and performance enhancements for external log-forwarding.
Description | Issues |
---|---|
The external log forwarder no longer removes escape characters in nested JSON log messages while streaming. |
SE-22519 |
Upgrades via proxy to Runtime Fabric agent version 1.11.x no longer fail. |
SE-23673 |
Additionally, this release includes fixes for security vulnerability CVE-2020-26160.
November 11, 2021
Description | Issues |
---|---|
Application pods no longer get restarted due to eviction if they exceed their ephemeral storage limit. |
SE-23476 |
November 5, 2021
Description | Issues |
---|---|
Application ingress via Edge did not work correctly after upgrading to 1.11.0. |
SE-23382 |
November 1, 2021
Runtime Fabric on VMs / Bare Metal now uses the rtf-runtime-registry
endpoint to retrieve the necessary Docker container image layers for running applications in Kubernetes. This change requires that you:
Allowlist the appropriate endpoint before installing or upgrading:
US control plane: rtf-runtime-registry.kprod.msap.io
EU control plane: rtf-runtime-registry.kprod-eu.msap.io
Restart applications after upgrading.
See the port IP addresses and hostnames to add to the allowlist and the upgrade documentation for instructions.
After upgrading, Runtime Fabric uses mutual authentication to connect to the Anypoint control plane when pulling application artifacts. This is the default behavior and requires that you allowlist specific endpoints before installing or upgrading to version 1.11.0. Refer to Mutual Authentication with Anypoint Platform and the upgrade documentation for instructions.
Description | Issues |
---|---|
Runtime Fabric ingress no longer sends duplicate |
SE-22825 |
Runtime Fabric ingress no longer sends a |
SE-23045 |
Runtime Fabric upgrades now process PKCS#12 pass phrases with special characters. |
SE-23235 |
This release corrects an issue in which Runtime Fabric could not validate pod security policies. If you you’re upgrading to this version, redeploy or restart your Mule applications. |
SE-22930 |
Additionally, this release includes fixes for the following potential security vulnerabilities:
CVE-2008-3109
CVE-2008-5347
CVE-2008-5349
CVE-2008-5352
CVE-2008-5358
CVE-2016-10750
CVE-2020-15999
CVE-2020-1971
CVE-2021-33503
CVE-2021-33910
CVE-2021-3449
CVE-2021-3711
September 20, 2021
This release adds support for Kubernetes version 1.20 for Runtime Fabric on Self-Managed Kubernetes.
Runtime Fabric now creates a separate Kubernetes Service Account for every application deployment. Previously Runtime Fabric created one Service Account per namespace.
This release of Runtime Fabric uses Fluent Bit 1.8.3 for external log forwarding. If you forward logs to Elasticsearch, you must set the Elasticsearch configuration parameter Generate_ID
to On
. By default, Fluent Bit sets this parameter to Off
.
To reduce the amount of incoming log data, Runtime Fabric now disables Anypoint Monitoring sidecar container metrics debug logs by default. To enable this change, you must restart your applications.
Description | Issues |
---|---|
Added security fixes to Runtime Fabric software component libraries. |
SE-21723, SE-21834, SE-21997 |
Containers for the external log-forwarder no longer continually restart and show a degraded status. |
SE-22021 |
Persistence Gateway no longer crashes with an |
SE-22015 |
When you create ingress for new applications, ingress templates with wildcard certificates now generate TLS sections. |
SE-22516 |
If application log forwarding is disabled for Titanium storage, Runtime Fabric no longer sends logs to Anypoint Monitoring. |
SE-20778 |
In the case of HTTP 429 responses from upstream, Runtime Fabric retries fetching application resources. |
SE-22065 |
August 12, 2021
Custom ingress resource templates for Runtime Fabric on Self-Managed Kubernetes
Using custom ingress resource templates enables you to take advantage of native Kubernetes ingress configuration functionality, including support for:
Multiple host names per application
Multiple ingress controllers within the same Runtime Fabric
TLS and HTTPS configuration
Custom URL naming
URL parameter placeholders
Refer to Configure Ingress for Runtime Fabric on Self-Managed Kubernetes for more information.
Description | Issue |
---|---|
Anypoint Runtime Fabric: Applied security fixes for critical and high vulnerabilities in Runtime Fabric components. |
RTF-2834 |
Anypoint Security Edge: Fixed the 502 Gateway issue with the HTTP HEAD method. |
SE-21704 |
Anypoint Security Edge: No longer allow mTLS bypass via request host header. |
SE-20207 |
Anypoint Security Edge: Remediated Oracle Java security vulnerabilities. |
SE-20592 |
When deploying new apps or redeploying existing apps to Anypoint Runtime Fabric, Runtime Manager now selects the latest date patch of the Mule runtime version, if applicable, by default.
During the grace period, you can select earlier date patches until they are no longer available. If you select an earlier date patch, and make any subsequent changes to that application, you might be required to update it to a later date patch.
For more information, see Mule Runtime Patch Updates for Runtime Fabric.
This release includes the following major enhancements and fixes:
Added: Support for Kubernetes version 1.19 for Self-Managed Kubernetes clusters.
Added: External log forwarding support for Datadog logging service.
Added: Patches for CVE-2020-15999, CVE-2020-1971, and CVE-2021-3449.
Updated: External log forwarding improvements for performance under load.
Updated: Logging improvements for Runtime Fabric agent logs.
Updated: Deprecated support for Kubernetes version 1.16 for Self-Managed Runtime Fabric clusters.
Fixed: Toggling the TLS option did not clean up the CA cert configuration for external log forwarding.
Fixed: External log forwarding issue with character escaping in JSON-formatted log messages.
Fixed: Intermittent SSL connection errors that occurred under stress load when using external log forwarding.
Fixed: Intermittent Resource not found
error occurred when toggling log forwarding.
Fixed: Persistence object store returned intermittent authorization errors.
This release includes the following fixed issues:
Issue | Description |
---|---|
SE-20667 |
Fixed Runtime Fabric Ingress issue on handling headers with more than 100 comma-separated fields. |
SE-20774 |
Dedicated ingress nodes do not forward logs when using external log forwarding. |
This release includes the following fixed issues:
Issue | Description |
---|---|
SE-20686 |
Fixed an issue that may prevent publishing logs to Anypoint Monitoring for existing applications after upgrading to version 1.9.1. |
This release includes the following major enhancement:
Added the Persistence Gateway that enables Mule applications deployed to a Mule runtime engine (Mule) to store and share data across Mule application replicas and application restarts. This feature is supported on both Runtime Fabric on Self-Managed Kubernetes and Runtime Fabric on VMs / Bare Metal.
This release includes the following fixed issues:
Issue | Description |
---|---|
SE-19462 |
Added support for the |
SE-19725 |
Fixed an issue that prevents logs from appearing in the console if the logger is configured with a |
SE-19374 |
Added support for default INFO logging to |
SE-18317 |
Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages. |
SE-20432 |
Fixed an issue where cluster health was degraded after switching to the new monitoring endpoint. |
This release includes the following major enhancement and bug fixes:
Added: Support for Runtime Fabric on Self-Managed Kubernetes with Google Kubernetes Engine (GKE).
Added: Security improvements for the resource-fetcher service.
Added: Support for Enhanced API Metrics with Anypoint Monitoring.
Added: Support for new Anypoint Monitoring endpoint (dias-ingestor) with port 443; the existing endpoint will be deprecated.
Fixed: Cluster health reporting may encounter issue when Anypoint Monitoring Log Forwarding is disabled.
This release includes the following major enhancements and bug fixes:
Added: External log forwarding support for Syslog logging service.
Added: Runtime Fabric and Anypoint Security Edge support for WebSockets.
Fixed: Runtime Manager reporting incorrect state in some cases, when multiple applications were deployed concurrently.
Fixed: OpsCenter CPU usage dashboard displaying only last 24 hours of CPU data.
Fixed: Application logs missing in Anypoint Monitoring in some occasions.