--- schema_version: "1" id: e08c1226b5f9345f8eaa4dd4040e23c22ad549c3bcfc4a0ccb3dc35933f5c3a9 title: Anypoint Runtime Fabric Command-Line Tool (rtfctl) BYOK Release Notes collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes.md canonical_url: https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: b82b65d3756bab2734bccc30b25cd3ace3f5e37c79bc6788180825624d846c90 description: MuleSoft Documentation Site latest: true --- # Anypoint Runtime Fabric Command-Line Tool (rtfctl) BYOK Release Notes The following release notes are for Runtime Fabric Command Line Tool (`rtfctl`) BYOK (Bring your own Kubernetes) version: The Runtime Fabric CLI is the installation and management utility tool for your Runtime Fabric running on Kubernetes. To download and install `rtfctl`, refer to [Install the Runtime Fabric Command Line Tool](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl). ## [](#1-0-150)1.0.150 **July 30, 2026** ### What’s New - `rtfctl` 1.0.150 introduces a new `rtfctl agent-truststore` command group. Inspect, back up, merge, and update the certificate authority (CA) certificates that the Runtime Fabric agent uses for mutually authenticated TLS (mTLS) connections to the Anypoint Platform control plane. This simplifies CA rotation, such as during a CA compromise or planned infrastructure change, without requiring additional tooling. For more information, refer to [Managing the Agent Truststore with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/manage-agent-truststore-rtfctl) and [Agent Truststore Commands](https://docs.mulesoft.com/runtime-fabric/latest/manage-agent-truststore-rtfctl#commands). ## [](#1-0-118)1.0.118 **March 11, 2026** ### Fixed Issues
Issue Resolution ID

rtfctl apply and rtfctl delete commands failed to manage secure properties if the property names contained certain suffixes or were malformed (for example, names containing literal strings like --value). The rtfctl utility is now updated with improved command-line argument parsing to correctly identify and process properties regardless of their name structure, ensuring that updates and deletions execute successfully

W-20497173
## [](#1-0-113)1.0.113 **December 8, 2025** ### What’s New - Anypoint Runtime Fabric Command-Line Tool (rtfctl) now supports the backup and restore of the Mule Application Custom Resource Definition (CRD).

Mule Application Custom Resources (CRs) aren’t supported for backup and restore. You must plan your recovery strategy using your source control repository as the single source of truth for all application configurations. After a Runtime Fabric cluster restore, you must re-apply your Mule Application CRs from your repository.
## [](#1-0-107)1.0.107 **September 03, 2025** ### What’s New - The `--core-software-only` flag in the rtfctl `restore` command enables you to restore only the core Runtime Fabric software components without triggering Mule app synchronization from the control plane. For details, refer to the [restore](https://docs.mulesoft.com/runtime-fabric/latest/rtfctl-reference#restore) command. ### Fixed Issues
Issue Resolution ID

The --core-software-only flag is now available in the rtfctl restore command.

W-19087426
## [](#1-0-98)1.0.98 **July 31, 2025** ### Fixed Issues
Issue Resolution ID

The clarity of ctl messages for rtctl validate and restore commands is now enhanced.

W-18181576, W-18109029

The validation prompt before restore in the case namespace no longer matches the backup.

W-12227576

This release includes security fixes.

W-18493468
## [](#1-0-92)1.0.92 **March 25, 2025** ### Fixed Issues
Issue Resolution ID

rtfctl commands no longer fail by missing Custom Resource Definitions (CRDs).

W-18024871
## [](#1-0-89)1.0.89 **March 10, 2025** ### What’s New - Anypoint Runtime Fabric Command-Line Tool now supports backup and restore of HTTP Route-Template CRD and CR. ### Fixed Issues
Issue Resolution ID

The --cluster-ops image flag taken from the local registry that is used to install the Runtime Fabric agent is now correctly configured.

W-16224293

rtfctl backup for OpenShift fabrics now considers the secrets required for the ingress resources.

W-17283597

The value for crds.install during helm migration is no longer explicitly set to false .

W-16452863

Informational output from Anypoint CLI now goes through stdout as in older versions.

W-16701108

Validation of the Anypoint user and bearer tokens is now run before initiating the backup phase in the rtfctl migrate flow.

W-16596517
## [](#1-0-79)1.0.79 **August 15, 2024** ### Fixed Issues
Issue Resolution ID

The rtfctl validate command no longer fails with a container unready error message when running jobs.

W-15895512
## [](#1-0-70)1.0.70 **June 7, 2024** ### What’s New - Starting with `rtfctl` version 1.0.70, if you use an rtf-agent version higher and equal to 2.6.52, the `rtfctl` backup bundle doesn’t contain the Mule app deployments. The deployments are synched 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). - The new `rtfctl renew-expired-client-cert` command renews an expired client certificate using a pre-downloaded package. Refer to [Commands for Configuring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl#configure-rtfctl). - The `rtfctl report` command has a new flag, `--release-name`, that specifies the name of the helm release to support installations using custom release names. Refer to [Report](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl#report) command documentation. ### Fixed Issues
Issue Resolution ID

The rtfctl report command now creates unique temporary directories for each process, eliminating conflicts from shared directory usage. Additionally, the command avoids overwriting existing reports unless you specify the --overwrite flag. For two concurrent reports to work, they need to have different report file names, for example:

./rtfctl report --debug --file report1.tgz --namespace rtf-test
./rtfctl report --file report2.tgz --namespace rtf-test

W-15618561
## [](#1-0-55)1.0.55 **May 13, 2024** ### What’s New - The `rtfctl report` command collects data on a best-effort basis. The command generates the report even if sub-tasks fails. ### Fixed Issues
Issue Resolution ID

The rtfctl report command collects data on a best-effort basis. The command generates the report even if sub-tasks fails.

W-15696698
## [](#1-0-47)1.0.47 **April 12, 2024** ### What’s New - The `rtfctl report` command is updated for OTel sidecar. ## [](#1-0-44)1.0.44 **March 7, 2024** ### What’s New - The `rtfctl report` command now outputs an additional JSON formatted file for resources in agent versions v2.6.0 and above. - The `rtfctl report`, `backup`, and `restore` commands now extends the support to `kubernetestemplate` resources used to customize your app deployments. ### Fixed Issues
Issue Resolution ID

The rtfctl test command now fails sooner when there are terminal errors and does not require you to wait until the operation times out.

W-14992372

For Helm based agent installations, rtfctl apply mule-license command now detects and provides a Helm command for you to execute.

W-14278334
## [](#1-0-29)1.0.29 **November 14, 2023** ### What’s New - Review new [RTFCTL Kubernetes permissions](https://docs.mulesoft.com/runtime-fabric/latest/rtfctl-permissions) documentation. - Review new [Auditing rtfctl Operations](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl#auditing) documentation. ## [](#1-0-20)1.0.20 **September 25, 2023** ### What’s New - The `rtfctl report` command now includes the Anypoint monitoring data of Mule deployments with the option `--include-mule-monitoring-data`. - The `rtfctl validate` command now supports `--image-pull-registry` and `--image-pull-secret` flags for validating against a local registry. ### Fixed Issues
Issue Resolution ID

The apply proxy command no longer returns an invalid warning message.

W-13032322

The restore operation now restores custom resources correctly.

W-13974770
## [](#1-0-12)1.0.12 **August 4, 2023** ### What’s New - Runtime Fabric now supports `rtfctl backup` and `rtfctl restore` commands for OpenShift clusters, refer to [Backing up and Restoring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-backup-restore) documentation. - You can now migrate to helm native Runtime Fabrics from `rtfctl`, refer to the [Migrating to Helm Managed Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/migrate-helm) documentation. ### Fixed Issues
Issue Resolution ID

The rftctl backup and rtfctl restore commands now work correctly with custom resources.

W-13285192

Applying an HTTP proxy setting configuration to the app namespace no longer applies the proxy setting in the Runtime Fabric namespace.

W-12981038
## [](#0-4-22)0.4.22 **May 9, 2023** ### What’s New - The `rtfctl report` command now generates a fast compression file archive by using the new flag `use-fast-compression`. - The `rtfctl report` command now executes tasks in parallel worker pools by using the new `workers` flag. - The `rtfctl report` command now lets you choose which application namespaces to report using `app-namespaces` flag. ### Fixed Issues
Issue Resolution ID

When running the rtfctl uninstall command, the system namespace now waits for deletion of all relevant namespaces.

W-13100550

Runtime Fabric now uses the correct reference to cluster-ops during installation.

W-13074624

Runtime Fabric now unblocks CPC deployments correctly.

W-13097851

Reported security vulnerabilities are fixed.

W-12692341

Runtime Fabric now exposes an endpoint that takes version as input and responds with a pre-signed URL to download the given version.

W-13075535
## [](#0-4-1)0.4.1 **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](https://docs.mulesoft.com/runtime-fabric/latest/install-multiple-instances) documentation. ### Fixed Issues
Issue Resolution ID

An issue with a transport layer check no longer occurs when an application firewall blocks AMQP traffic while allowing HTTP/Websockets. Now the test attempts to validate the accessibility of the transport layer endpoint by sending actual AMQP frames over Websockets.

W-11958442

The rtfctl test outbound-network now works correctly for appliance-based clusters.

W-12499930

Backups of multiple instances created with rtfctl backup command can now be restored.

W-12742772
## [](#0-3-198)0.3.198 **January 23, 2023** ### Fixed Issues
Issue Resolution ID

The backup and restore commands now work correctly with persistence gateway resources.

W-11987155

The report command no longer reports non-RTF related namespaces.

W-12197726

The package command no longer fails when used with the -heap-dump flag.

W-11235954
### Known Issues
Known Issue Workaround ID

rtfctl restore command fails with segmentation fault.

Upgrade to the latest rtfctl version.

W-11987155
## [](#0-3-191)0.3.191 **December 15, 2022** ### Fixed Issues
Issue Resolution ID

Fixed security vulnerabilities.

W-12049033
## [](#0-3-179)0.3.179 **November 17, 2022** ### Fixed Issues
Issue Resolution ID

This release improves help messages on the command line.

W-11955726
## [](#0-3-175)0.3.175 **November 8, 2022** ### Fixed Issues
Issue Resolution ID

This release improves message formatting.

W-11174874, W-11942966

The rtfctl backup command now supports concurrent user execution and deletes the tmp/backup directory when the backup completes.

W-11063729

Clusters in the EU control plane are properly connected to the Anypoint Platform control plane after upgrading.

W-11227117
## [](#0-3-168)0.3.168 **May 24, 2022** ### What’s New - This release improves the example of how to use the `renew-expired-client-cert` command. - The `package` command now requires a mandatory argument for the path to the directory where the file will be created. ### Fixed Issues
Description Issue

The apply system-configuration command no longer fails because of a permission issue.

W-10993223

The package command no longer fails with an incorrect directory path error on Windows.

W-10810849
## [](#0-3-160)0.3.160 **April 5, 2022** ### Fixed Issues
Description Issue

This release includes improvements to support multiple authentication providers.

SE-24124

rtfctl now allows a custom pull-secret-name for local registries.

N/A

This release improves rtfctl documentation examples.

W-10647420
## [](#0-3-157)0.3.157 **February 22, 2022** ### What’s New - To support local registries in Runtime Fabric on Self-Managed Kubernetes version 1.12.0 and later, the `rtfctl` utility now includes the `get registry-credentials` command. Additionally, the `rtfctl install` command now includes the following flags: - `--image-pull-registry` - `--image-pull-secret` ## [](#0-3-145)0.3.145 **November 1, 2021** ### What’s New - You can now run the `rtfctl test outbound-network` command on all nodes or on a specific node. ### Fixed Issues
Description Issue

The rtfctl test outbound-network command allows network checks on all nodes or on specific nodes per the node selector.

SE-22084
## [](#0-3-139)0.3.139 **October 12, 2021** ### What’s New - The `rtfctl report` command now captures any previous container logs in a separate file. - The `rtfctl backup` and `rtfctl restore` commands are now compatible with Kubernetes 1.20. ### Fixed Issues
Description Issue

The rtfctl utility now reads both NO_PROXY and no_proxy settings from the environment.

SE-22108

The rtfctl proxy command throws an error if the RTF namespace is not present when the command applies proxy settings.

RTF-2933
## [](#0-3-135)0.3.135 **August 12, 2021** ### What’s New - The `rtfctl apply ingress-configmap` command is deprecated. If you attempt to apply an ingress ConfigMap with `rtfctl` against Runtime Fabric 1.10 or later, Runtime Fabric rejects the request. - The latest version of `rtfctl` includes backup and restore support for ingress resource templates. Use `rtfctl report` to see details about the ingress resource templates you applied. ### Fixed Issues
Issue Number

The rtfctl apply secure-property command now allows = for single-line values.

SE-22118

The rtfctl report no longer fails due to old pull secret references on old Runtime Fabric clusters.

SE-21254
## [](#jun-24-2021-0-3-128)Jun 24, 2021 (0.3.128) This release includes the following enhancements and bug fixes: - Added: The `rtfctl apply secure-property` command now handles special characters in a value. - Fixed: The `rtfctl get secure-properties` command no longer fails when retrieving values that have a '\\n' character. - Fixed: The `rtfctl report` command now captures all container logs. ## [](#apr-22-2021-0-3-122)Apr 22, 2021 (0.3.122) This release includes the following enhancements and bug-fixes: - Added: Improvement to the `rtfctl report` command to include information about persistent gateway deployment. - Added: Enhancement to the `rtfctl backup` and `rtfctl restore` commands to handle persistent gateway configuration and deployment. - Fixed: Issue where `rtfctl uninstall` may fail on gravity clusters. - Fixed: Issue where the state file for binary upgrade check was not created in the user’s home directory. ## [](#mar-18-2021-0-3-103)Mar 18, 2021 (0.3.103) This release includes the following major enhancement(s): - Added: The `rtfctl report` command includes runtime fabric helm history information. - Added: Enhancements to the `rtfctl status` command to fetch information from inside the runtime fabric cluster (Self-Managed Kubernetes only). - Added: Outbound Network tests now include both legacy and new Anypoint Monitoring endpoint(s). ## [](#feb-10-2021-0-3-102)Feb 10, 2021 (0.3.102) This release includes the following major enhancement(s): - Added: Improvements to capture logs from previous container restarts in the debug report. - Added: Enhancement to backup and restore any gravity custom resources created for smtp and log-forwarder. - Fixed: Issue where `rtfctl restore` command would throw an error while restoring on the same Self-Managed Kubernetes cluster where the backup was taken. ## [](#dec-16-2020-0-3-94)Dec 16, 2020 (0.3.94) This release includes the following major enhancement(s): - Added: `rtfctl status dns-check` command to test DNS health (Self-Managed Kubernetes only). - Added: `rtfctl delete secure-properties` command to remove secure properties. - Fixed: `rtfctl validate` command shows overall validation status message (Self-Managed Kubernetes only). - Fixed: `rtfctl` commands `help` and `version` now works without having Kubernetes context. ## [](#nov-23-2020-0-3-87)Nov 23, 2020 (0.3.87) This release includes the following major enhancement(s): - Added: `rtfctl validate` command to validate the Kubernetes environment prior to installing Runtime Fabric (Self-Managed Kubernetes only). - Added: `rtfctl apply ingress-configmap` command to apply ingress configuration on Runtime Fabric (Self-Managed Kubernetes only). - Added: `rtfctl uninstall` command to uninstall Runtime Fabric. - Fixed: bug fixes and improvements. ## [](#see-also)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)