Anypoint Runtime Fabric is a container service that allows you to run Mule applications, composite APIs and API gateways across any environment with centralized management via Anypoint Platform. Some of the capabilities of Anypoint Runtime Fabric include: Isolation between applications by running a separate Mule runtime server per application. Ability to run multiple versions of Mule runtime server on the same set of resources. Scaling applications across multiple replicas. Automated application fail-over. Application management with Anypoint Runtime Manager.

1. Thursday, May 12th 2022
Washington, DC MuleSoft Meetup
Group
Anypoint Runtime Fabric on Self-Managed
Kubernetes

2. 2
5:30 PM: Introductions & Welcome
5:45 PM: Mani Rautroy, Senior Technical Architect @ XTIVIA
Anypoint Runtime Fabric on Self-Managed Kubernetes
6:45 PM: Closing Q&A & Networking
Agenda

3. 3
About the organizer:
● Akkiraju Ivaturi, Sr. Systems Engineer at GEICO
● Over 19 years of experience in IT and 8 years in MuleSoft
● Based outside of Maryland
● Enjoy spending time reading blogs and technical articles
● Love blogging, sharing technical articles
Co-organizers:
● Sivakumar Muthu
● Benjamin Stone
Introductions

4. 4
● Need more speakers. Please feel free to volunteer for the future meetups.
● What do you expect from these meetups? Please send us an email with your expectations and we
will make sure that the events reflects the same.
● Anything else, just send us an email.
Request to all members

5. Before we begin…
1. Please mute your microphone
2. Use the live chat feature to ask questions or
hold until the end

6. Mani Rautroy, Senior Technical Architect @ XTIVIA
Anypoint Runtime Fabric on Self-
Managed Kubernetes

7. Anypoint Runtime Fabric Overview
Anypoint Runtime Fabric is a container service that allows you to
run Mule applications, composite APIs and API gateways across any
environment with centralized management via Anypoint Platform.
Some of the capabilities of Anypoint Runtime Fabric include:
 Isolation between applications by running a separate Mule
runtime server per application.
 Ability to run multiple versions of Mule runtime server on the
same set of resources.
 Scaling applications across multiple replicas.
 Automated application fail-over.
 Application management with Anypoint Runtime Manager.

8. RTF on VM/Bare Metal
(Production
Configuration)
Runtime Fabric – VM/Bare Metal vs Self-
Managed
RTF on AKS/EKS/GKE (Default
Configuration)
Option 1 Option 2
Ingress
controller
Ingress
controller
App
3
Mule
App
4
Mule
App
1
Mule
App
2
Mule
App
5
Mule
App
6
Mule
App
1
Mule
App
2
Mule
App
7
Mule
App
8
Mule
App
5
Mule
App
6
Mule
TCP load balancer
Control
plane
Agent
AKS or EKS or GKE
All contents © MuleSoft,
LLC

9. Use case for Self Managed Kubernetes & Bare
Metal/VMs
● Runtime Fabric on Self-Managed Kubernetes:
 Your IT platform runs on AWS, Azure or GCP and leverages various IaaS,
PaaS and SaaS services.
 IT Team is well versed with Docker/Kubernetes
● Runtime Fabric on Bare Metal/VMs:
 Regulatory requirements prohibits the use of any public cloud.
 Wants to get the CloudHub like feature on Prem.
 IT Team is relatively new to Docker/Kubernetes

10. Management options for
Anypoint Runtime Fabric
1. Runtime Fabric on Self-Managed Kubernetes: a
version of Runtime Fabric that you install on an
existing Kubernetes environment that you operate
and manage. This version supports Amazon Elastic
Kubernetes Service (Amazon EKS), Azure
Kubernetes Service (AKS), and Google Kubernetes
Engine (GKE).
2. Runtime Fabric on VMs / Bare Metal: a version of
Runtime Fabric where MuleSoft provides required
software infrastructure components, including
Docker and Kubernetes. You install this version on
virtual machines that you operate and manage.
Runtime Fabric
Option
IT Administrator
MuleSoft Organization
Administrator
Self-Managed
Kubernetes
Requires an IT administrator to create
and configure a Kubernetes cluster
on Amazon EKS, AKS, or GKE. This
persona is also responsible for
installing Runtime Fabric and
managing Kubernetes.
Creates Runtime Fabrics,
deploys applications, and
performs other tasks
within Anypoint
Platform
VMs / Bare
Metal
Creates and configures the
infrastructure that runs Runtime
Fabric. This persona is also
responsible for installing Runtime
Fabric and maintaining the underlying
infrastructure during its operation.
Creates Runtime Fabrics,
deploys applications, and
performs other tasks
within Anypoint
Platform

11. Feature Support Matrix for Runtime Fabric
on Self-Managed Kubernetes & Runtime
Fabric on VMs / Bare Metal
Features
Runtime Fabric on Self-Managed
Kubernetes
Runtime Fabric on VMs / Bare
Metal
Support for deploying Mules and API
Gateways
Supported Supported
Kubernetes and Docker
Not included.
Provide your instances of Kubernetes
and Docker via Amazon EKS, AKS or
GKE clusters.
Included
Installing on any Linux distribution Supported Support for RHEL and CentOS only
Node auto-scaling
Supported using AWS, Azure or Google
Cloud functionality
Not supported
External log forwarding
You must provide an external log
forwarding service
Included
Internal load balancer
You must provide an internal load
balancer (Ingress Controller)
Included
Anypoint Security Edge Not supported Supported
Ops Center
Not Included
You can enable monitoring and alerting
in AWS, Azure, or Google Cloud

12. Architecture: Runtime Fabric on Self-Managed
Kubernetes

13. Management Responsibility
The successful operation of
Anypoint Runtime Fabric on
Self-Managed Kubernetes is a
shared responsibility. It is
critical to understand which
areas you must manage and
which areas are managed by
MuleSoft.
This image illustrates different
MuleSoft and customer
responsibilities for on-premises
Runtime Fabric instances:

14. Ingress Controller

15. 1
● Anypoint Runtime Fabric on Self-Managed Kubernetes enables you to specify custom Ingress
configurations using an ingress resource template. In a template, similar to a Kubernetes ingress
spec, you can specify annotations, ingress class name, and HTTP and HTTPS rules.
○ Using custom ingress resource templates in Runtime Fabric enables you to take advantage of
native Kubernetes ingress configuration functionality, including support for:
■ Multiple ingress controllers within the same Runtime Fabric instance
■ Multiple ingress configurations available to choose per application
■ TLS and HTTPS configuration
■ URL parameter placeholders
■ Custom URL Naming
Ingress for RTF on Self-Managed K8s

16. How Ingress Resources Templates Work in Runtime
Fabric

17. Demo

18. Demo Outline
Create an AKS
Cluster
Install Runtime Fabric on AKS Cluster
Configuring Ingress Controller
Deploy a Mule Application
Secure the traffic from client to the
Ingress
Secure the traffic from the Ingress to the
backend API
Uninstall/Cleanup
2
1
3
4
5
6
7

19. Prerequisites
● Anypoint Platform - We’ll need an Anypoint Platform account to create our
Runtime Fabric service. You can sign up for a free trial account.
https://anypoint.mulesoft.com/login/signup?apintent=generic
● Azure CLI - A cross-platform command-line tool to connect to Azure
and execute administrative commands on Azure resources.
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
● kubectl - A command line tool for working with Kubernetes clusters.
https://kubernetes.io/docs/tasks/tools/
● rtfctl - A command line tool to locally manage Runtime Fabrics
https://docs.mulesoft.com/runtime-fabric/1.10/install-rtfctl
● curl - A command line tool for transferring data using various network protocols
https://curl.se/download.html

20. Securing the End to End
Traffic

21. 21
Question 1:
From the following template which configuration(s) is/are key to make the traffic between Ingress
Controller and Hello-world application secure.
1: Line 5: nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
2. Line 22 , 23 and 24 backend:service:name
3. Line 14: secretName: example-tls
4: All of the above
Quiz time

22. 22
Question 2:
Which of the following is a unique feature of RTF on kubernetes compared to RTF on
baremetal/VM/appliance.
1. Isolation between applications by running a separate Mule runtime server per application.
2. Scaling applications across multiple replicas.
3. Scaling applications across multiple nodes.
4. Ability to run multiple versions of Mule runtime server on the same set of resources.
Quiz time

23. 23
Question 3:
What is the best option for log forwarding if you have a Titanium subscription. Select all that apply
1. Use ‘kubectl logs’ to view logs
2. Use Anypoint Monitoring
3. Use OpsCentre for monitoring the pod logs
4. Use Splunk for Kubernetes to forward logs and visualize
Quiz time

24. Introduce yourself to the group
General Q&A & Networking