The document discusses Runtime Fabric (RTF) and its capabilities on Red Hat OpenShift. Key points include: - RTF 2.x introduced support for running on OpenShift through authorized namespaces, allowing shared tenancy without a dedicated cluster. - OpenShift is a Kubernetes distribution optimized for containers and supported in both cloud and self-managed environments. - When running RTF on OpenShift, the RTF services run in pods managed by the OpenShift container platform, while applications are deployed as Kubernetes resources. - The demo shows installing CodeReady Containers to run OpenShift locally, deploying RTF through the operator, and configuring ingress to expose applications.

1. Wednesday 14/12/2022
Runtime Fabric Series (From
Zero to Hero) - Sessione 3
RTF on OpenShift

2. All contents © MuleSoft, LLC
Safe harbor statement
The information in this presentation is confidential and proprietary to MuleSoft and may not be disclosed without the
permission of MuleSoft. This presentation is not subject to your license agreement or any other service or subscription
agreement with MuleSoft. MuleSoft has no obligation to pursue any course of business outlined in this document or any
related presentation, or to develop or release any functionality mentioned therein. This document, or any related
presentation and MuleSoft's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by MuleSoft at any time for any reason without notice. The
information on this document is not a commitment, promise or legal obligation to deliver any material, code or functionality.
This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational
purposes and may not be incorporated into a contract. MuleSoft assumes no responsibility for errors or omissions in this
document, except if such damages were caused by MuleSoft intentionally or grossly negligent.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

3. All contents © MuleSoft, LLC 3
Introductions
Speakers
Moderators

4. All contents © MuleSoft, LLC
1. RTF 2.x
2. Red Hat OpenShift Overview
3. RTF on OpenShift
4. Demo
5. Q&A
6. Trivia Quiz

5. All contents © MuleSoft, LLC
RTF 2.x
Introduced Features

6. All contents © MuleSoft, LLC
Authorized Namespaces: shared tenancy - no
need anymore for a dedicated K8S Cluster to host
RTF
● RTF can run in parallel to other workloads into
a dedicated set of Namespaces (rtf +
environment specific ones)
● No clear support as of today for multiple RTF
instances on same Cluster
Support of Red Hat OpenShift (4.6 to 4.10): both
Cloud and Self-managed options supported (see
later for exact matrix)
Note: branching for Appliance flavour (still on v1.13)
Runtime Fabric 2.0
GA September 13th, 2022
RTF 2.0 - Release note

7. All contents © MuleSoft, LLC
Protected Properties Values: values can now
be protected via Runtime Manager. These
properties are injected into the application, but
not encrypted.
Custom log4j2 config: further possibility for log
forwarding setup
Runtime Fabric 2.1
GA November 8th, 2022
RTF 2.1 - Release note

8. All contents © MuleSoft, LLC
Red Hat OpenShift
Overview

9. All contents © MuleSoft, LLC
DIY Container Stack Challenges

10. All contents © MuleSoft, LLC
Red Hat OpenShift Editions
Self Managed OpenShift Proposition

11. All contents © MuleSoft, LLC
Cloud Native Red Hat vs. xKS
Red Hat OpenShift

12. All contents © MuleSoft, LLC
Cloud Native Red Hat vs. xKS
Red Hat OpenShift

13. All contents © MuleSoft, LLC
RTF on OpenShift

14. All contents © MuleSoft, LLC
Anypoint Runtime Fabric
Server Server
Mule
App
Mule
App
Mule
App
Mule
App
Server
Mule
App
Mule
App
Server
Mule
App
Mule
App
Server
Mule
App
Mule
App
Server
Mule
App
Mule
App
Runtime Fabric services
Docker & Kubernetes (nodes)
HL Architecture
Anypoint Platform
API-led connectivity for microservices
Internal & External APIs
RUNTIME
MANAGER
ACCESS
MANAGEMENT
MANAGEMENT
CENTER
VISUALIZER
ADVANCE
MONITORING
EXCHANGE
PARTNER
MANAGER`
API DESIGNER
ANYPOINT
SECURITY
DESIGN
CENTER
Openshift Container Platform

15. All contents © MuleSoft, LLC
Supported Distributions
Start quickly with
Redhat managed
services
Get control and
flexibility with self
managed offering
200+ validated
integrations and certified
container ecosystem

16. All contents © MuleSoft, LLC
Shared Responsibility Model

17. All contents © MuleSoft, LLC
Demo

18. All contents © MuleSoft, LLC
CodeReady Containers (CRC)
OpenShift installation
● Install crc from the following link https://console.redhat.com/openshift/create/local and copy the pull
secret, it is necessary during installation
● Start crc : $ crc start
● You can access to OpenShift Container Platform web console using your web browser:
$ crc console
● There are two different credentials:
○ developer user : for creating projects or OpenShift applications and for application
○ deployment kubeadmin user: for administrative tasks such as creating new users or setting
roles
● You can view the password for the developer and kubeadmin user by running:
$ crc console --credentials

19. All contents © MuleSoft, LLC
CodeReady Containers (CRC)
OpenShift on your laptop
Link to installation console: https://console.redhat.com/openshift/create/local

20. All contents © MuleSoft, LLC
CodeReady Containers (CRC)
OpenShift installation
● It is possible to access the OpenShift cluster with the OpenShift CLI
$ crc oc-env
$ eval $(crc oc-env)
$ oc login -u developer https://api.crc.testing:6443
● You can list all projects in the CRC instance:
$ oc projects
● You can navigate between projects:
$ oc project <nameOfTheProject>

21. All contents © MuleSoft, LLC
Install RTF
● Create a deployment target for Mule apps, select OpenShift Container Platform
● Create a namespace which provides a mechanism to scope resources in a cluster
$ oc create ns rtf
● Create a pull secret for pulling Docker images from Runtime Fabric registry, copy the
instruction provided by Mulesoft
$ oc create secret docker-registry <pull_secret> --namespace rtf --docker-
server=<docker_registry_url> --docker-username=<docker_registry_username> --docker-
password=<docker_ registry_password>
● Using the OperatorHub to install Runtime Fabric Operator.
● Configure the operator, in the console switch the value of Project to the rtf namespace
and create an instance. You need to provide activationData and your company’s Mule
license key Base64 encoded.

22. All contents © MuleSoft, LLC
Ingress controller configuration
Install RTF
● Configure ingress controller: OpenShift includes a built-in ingress controller operator,
create a ingress template using the configuration:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
name: rtf-ingress
namespace: rtf
labels:
mule-environment: environment-id
mule-business-group: business-group-id
spec:
ingressClassName: rtf-openshift-default
rules:
- host: app-name.router-internal-default.apps-crc.testing
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: service
port:
number: 80
● The template can be created:
$ oc create -f ingress_template.yaml

23. All contents © MuleSoft, LLC
Deploy
● Enter a unique name as the
Application Name
● Select the OpenShift RTF deployment
target
● Import File from Exchange or select
Upload File
● Set the configuration for the
application (Replica size, Replicas)
● Deploy Application

24. All contents © MuleSoft, LLC
OpenShift specific artifacts - Routes
RTF on OpenShift
Providing additional features in respect to canonical k8s Ingress (still
relying on k8s Services)
OpenShift implements the Ingress Controller with a shared Router
service that runs as a pod inside the cluster (based on HAProxy)
1.
1.
2.
2.
OS Networking

25. All contents © MuleSoft, LLC
OpenShift specific artifacts - Routes
RTF on OpenShift
Canonical router hostname for CRC - router-
default.apps-crc.testing
Affecting application url (it must be configured in your
Ingress Template)
3.
3.
4.
4.

26. All contents © MuleSoft, LLC
Q&A

27. All contents © MuleSoft, LLC
Trivia Quiz

28. All contents © MuleSoft, LLC
Thank you!