What are the minimum requirements for runtime fabric?

To ensure optimal performance, Runtime Fabric installation requires at least two nodes each equipped with: Minimum of two CPU cores. At least 15 GiB of RAM. At least 250 GiB of available disk space.

What can be used to deploy to runtime fabric?

In addition to using Anypoint Runtime Manager, to deploy applications to Anypoint Runtime Fabric, you can also deploy applications by using the Mule Maven plugin .

Why do we use runtime fabric?

Anypoint Runtime Fabric enables you to deploy Mule applications and API proxies to a Kubernetes cluster that you create, configure, and manage . If you work in public clouds and have some level of expertise in managing a Kubernetes cluster, Runtime Fabric supports: Amazon Elastics Kubernetes Service (EKS)

What is a runtime fabric?

Anypoint Runtime Fabric is a container service that automates the deployment and orchestration of Mule applications and API gateways . Learn more about the topic covered in this video, and expand your skills further with the following course developed by MuleSoft experts - Development Fundamentals: https://sfdc.co/tnR5f.

Is Mule RTF better than CloudHub?

For those seeking a fully managed service with a global presence and auto-scaling capability, CloudHub 2.0 is a fantastic option. RTF, on the other hand, is a better option if you need more control over your deployment environment and data or if you are already invested in container technology.

How do I deploy an application to Hyperledger fabric?

Step one: Decide on your network configuration. Step two: Set up a cluster for your resources. Managing your infrastructure. Step three: Set up your CAs. Planning for a CA. ... Step four: Use the CA to create identities and MSPs. Step five: Deploy peers and ordering nodes. Creating a peer. ... Next steps.

What are the system requirements for Minecraft fabric?

Fabric system requirements state that you will need at least 2 GB of RAM . Additionally, the game developers recommend somewhere around 4 GB of RAM in your system. You will need at least 150 MB of free disk space to install Fabric. Make sure your have 300 MB of free disk space in order to install Fabric.

What are the limitations of RTF?

For example, they cannot retain certain types of formatting, like Track Changes or comments . Additionally, they may not support certain kinds of images or objects. However, despite these limitations, RTF files remain an excellent way to transfer documents between different word processing programs or operating systems.

What are the limitations of MuleSoft?

Existing users cannot self-register . They must use an identity provider to access the portal. The API Experience Hub package is installed in the sandbox and production environments on the same date. As a result, you cannot use your sandbox organization for testing in the development cycle.

What is the difference between RTF and CloudHub?

MuleSoft RTF is a container service for multi-cloud and hybrid deployments. RTF allows you to deploy Mule applications and API gateways within a data center or any cloud platform, thus providing more flexibility than CloudHub .

Install Runtime Fabric on Self-Managed Kubernetes (2024)

Homepage
Runtime Fabric (1.10)
On Self-Managed Kubernetes
Install Runtime Fabric on Self-Managed Kubernetes

This version of the product has reached End of Life. You can switch to thelatest version.

Installing Runtime Fabric on Self-Managed Kubernetes requires tasks that must be performed by both IT administrators and MuleSoft organization administrators.

Anypoint Runtime Fabric can be installed and operated on an Amazon Elastic Kubernetes Service (Amazon EKS), Azure Kubernetes Service (AKS) or Google Kubernetes Engine (GKE) installation that you manage.

Before you Begin

Before installing Anypoint Runtime Fabric in a self-managed Kubernetes environment, ensure the following:

You have read and understand the architecture and requirements outlined in Runtime Fabric on Self-Managed Kubernetes
You have installed and configured your Kubernetes environment as follows:
- Running an EKS, AKS, or GKE Kubernetes environment. Other Kubernetes environments are not supported.
- Running on of the following Kubernetes versions:
  - 1.17.x
  - 1.18.x
  - 1.19.x
  - 1.20.10 or later patch versions on 1.20.x
- Running an ingress controller to send external requests to applications.

Step 1: Configure your Network to Support Runtime Fabric on Self-Managed Kubernetes

Network configuration must be performed by an IT administrator.

Before installing or using Runtime Fabric on Self-Managed Kubernetes, ensure that the following ports and hostnames are configured correctly.

Port Configuration

To install or run Runtime Fabric, ensure that you have configured the following ports on your Kubernetes installation:

Port	Layer 4 Protocol	Layer 5 Protocol	Source	Destination	Description
443	TCP	HTTPS	Internet	All nodes	Allow inbound requests to Mule runtime servers
443	TCP	AMQP over WebSockets	All nodes	Internet	Anypoint Platform management services
443	TCP	HTTPS	All nodes	Internet	API Manager policy updates, API Analytics Ingestion, and Resource retrieval (application files, container images).
443 (v1.8.50, or later)	TCP	Lumberjack	All nodes	Internet	Anypoint Monitoring, Anypoint Visualizer
5044 (deprecated)	TCP	Lumberjack	All nodes	Internet	Anypoint Monitoring, Anypoint Visualizer This port and hostname are deprecated in Anypoint Runtime Fabric, version 1.8.50 and later. If you are using a previous version of Anypoint Runtime Fabric you must add this port your allow list. If you are using a newer version, use the port and hostname specified above.

Port Used by the Persistence Gateway

The Persistent Gateway requires a Postgres-compliant database to store persistent data across Mule application replicas. Ensure that your Kubernetes cluster has access to this database and port. See Persistence Gateway.

Hostname Configuration

To function correctly, Runtime Fabric on Self-Managed Kubernetes requires the following hostname configurations:

Port	Protocol	Hostnames	Description
443	AMQP over WebSockets	US control plane: transport-layer.prod.cloudhub.io EU control plane: transport-layer.prod-eu.msap.io	Runtime Fabric message broker for interaction with the control plane.
443 (v1.8.50, or later)	TCP (Lumberjack)	US control plane: `dias-ingestor-router.us-east-1.prod.cloudhub.io` EU control plane: `dias-ingestor-nginx.prod-eu.msap.io`	Anypoint Monitoring agent for Runtime Fabric.
5044 (deprecated)	TCP (Lumberjack)	US control plane: dias-ingestor-nginx.prod.cloudhub.io EU control plane: dias-ingestor-nginx.prod-eu.msap.io	Anypoint Monitoring agent for Runtime Fabric. This port and hostname are deprecated in Anypoint Runtime Fabric, version 1.8.50 and later. If you are using a previous version of Anypoint Runtime Fabric you must add this port and hostname to your allow list. If you are using a newer version, use the port and hostname specified below. This is applicable to endpoints in both the US and EU clouds.
443	HTTPS	anypoint.mulesoft.com	Anypoint Platform for pulling assets.
443	HTTPS	kubernetes-charts.storage.googleapis.com	Kubernetes base charts repository.
443	HTTPS	docker-images-prod.s3.amazonaws.com	Kubernetes base charts repository.
443	HTTPS	US control plane: worker-cloud-helm-prod.s3.amazonaws.com EU control plane: worker-cloud-helm-prod-eu-rt.s3.amazonaws.com worker-cloud-helm-prod-eu-rt.s3.eu-central-1.amazonaws.com	Runtime Fabric version repository. The Runtime Fabric installation uses software from this repository during installation and upgrades.
443	HTTPS	US control plane: exchange2-asset-manager-kprod.s3.amazonaws.com EU control plane: exchange2-asset-manager-kprod-eu.s3.amazonaws.com exchange2-asset-manager-kprod-eu.s3.eu-central-1.amazonaws.com	Anypoint Exchange for application assets.
443	HTTPS	US control plane: rtf-runtime-registry.kprod.msap.io EU control plane: rtf-runtime-registry.kprod-eu.msap.io	Runtime Fabric Docker repository.
443	HTTPS	US control plane: prod-us-east-1-starport-layer-bucket.s3.amazonaws.com prod-us-east-1-starport-layer-bucket.s3.us-east-1.amazonaws.com EU control plane: prod-eu-central-1-starport-layer-bucket.s3.amazonaws.com prod-eu-central-1-starport-layer-bucket.s3.eu-central-1.amazonaws.com	Runtime Fabric Docker image delivery.
443	HTTPS	US control plane: runtime-fabric.s3.amazonaws.com EU control plane: runtime-fabric-eu.s3.amazonaws.com	Runtime Fabric Docker repository.
443	HTTPS	US control plane: configuration-resolver.prod.cloudhub.io EU control plane: configuration-resolver.prod-eu.msap.io	Anypoint Configuration Resolver.

Certificate Configuration

To allow different endpoints to use mutual TLS authentication to establish a connection, you must configure SSL passthrough to allow the following certificates:

Control Plane	Certificates
US control plane	transport-layer.prod.cloudhub.io configuration-resolver.prod.cloudhub.io
EU control plane	transport-layer.prod-eu.msap.io configuration-resolver.prod-eu.msap.io

Step 2: Create a Runtime Fabric using Runtime Manager

The procedures in this section should be performed by a MuleSoft organization administrator.

To install Runtime Fabric on Self-Managed Kubernetes, first create a Runtime Fabric using Runtime Manager. This is required to obtain the activation data which is needed during installation.

From Anypoint Platform, select Runtime Manager.
Click Runtime Fabrics.
Click Create Runtime Fabric.
Enter the name of the new Runtime Fabric, then select one of the following options:
- Amazon Elastic Kubernetes Service
- Azure Kubernetes Service
Click Next.
Review the Support responsibility disclaimer, then if you agree click Accept.
Runtime Manager creates the Runtime Fabric and displays the Activation State page. This page displays the activation data used to install Runtime Fabric on a Kubernetes service. Copy this data to the clipboard for use in the next section.

Step 3: Download the rtfctl Utility

The tasks in the section must be performed by an IT administrator.

Runtime Fabric on Self-Managed Kubernetes uses the rtfctl command-line utility for installation and management tasks. See Install the Runtime Fabric Command Line Tool.

Download the rtfctl command-line utility:

rtfctl is supported on Windows, MacOS (Darwin), and Linux. Download this utility using the URLs below:

Windows:

curl -L https://anypoint.mulesoft.com/runtimefabric/api/download/rtfctl-windows/latest -o rtfctl.exe

MacOS (Darwin):

curl -L https://anypoint.mulesoft.com/runtimefabric/api/download/rtfctl-darwin/latest -o rtfctl

Linux:

curl -L https://anypoint.mulesoft.com/runtimefabric/api/download/rtfctl/latest -o rtfctl

Step 4: Install Runtime Fabric

The procedures in the section must be performed by an IT administrator.

After creating a Runtime Fabric in Runtime Manager and obtaining the activation data, install Runtime Fabric into your Kubernetes service using the rtfctl command-line utility.

If your Kubernetes configuration is not located in the \~/.kube/config directory, set the KUBECONFIG environment variable before running rtfctl:

export KUBECONFIG=<path-to-kubeconfig>

Validate that your Kubernetes environment is read for installation:
```
rtfctl validate <activation_data>
```
The validate option verifies that:
- The Kubernetes environment is running.
- All required components exist.
- All required services are available.
  The rtfctl command-line utility outputs any incompatibilities with the Kubernetes environment.
Install Runtime Fabric:
```
rtfctl install <activation_data>
```
<activation_data> is the activation data obtained after creating the Runtime Fabric using Runtime Manager. During installation, the rtfctl utility displays any errors encountered.

Step 5: Insert the Mule License Key

The procedures in the section must be performed by an IT administrator.

After the installation has completed succesfully, insert the Mule license key.

Base64 encode the new Mule .lic license file provided by MuleSoft:
- On MacOS, run the following command:
  base64 -b0 license.lic
- On Unix, run the following command:
  base64 -w0 license.lic
- On Windows, a shell terminal emulator (such as cygwin) or access to a Unix-based computer is required.
  1. Transfer to your Unix environment if necessary.
  2. Run the following command to Base64 encode the license key:
    base64 -w0 license.lic

Insert the Mule license key:

rtfctl apply mule-license BASE64_ENCODED_LICENSE

To verify the Mule license key has applied correctly, run:
```
rtfctl get mule-license
```

Step 6: Configure the Ingress Resource Template

The procedures in this section should be performed by an IT administrator.

If your ingress controller requires custom annotations and ingress class definition, follow the instructions in Defining a Custom Ingress Configuration.

For GKE customers, the ingress controller included with GKE will provision a separate HTTP load balancer per application by default. Please read this KB article for more details.

Step 7: Validate Your Runtime Fabric