Toronto Virtual Meetup # 17 - Anypoint Runtime Fabric on Self-Managed Kubernetes

1. 4/21/2022
Toronto MuleSoft Meetup Group
Anypoint Runtime Fabric on Self Managed Kubernetes

2. 2
● About the organizers:
○ Anurag Dwivedi
● About the Speaker:
○ Mani Rautroy, Integration Architect, XTIVIA Inc
Introductions
A SHOW OF HANDS:
Who is new to this Meetup?

3. 3
 Anypoint Runtime Fabric on Self Managed Kubernetes
 Demo
Agenda

4. Anypoint Runtime Fabric on Self
Managed Kubernetes

5. 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.

6. 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

7. 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

8. 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

9. Architecture: Runtime Fabric on Self-Managed
Kubernetes

10. 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:

11. AsyncAPI Specification Demo – Anypoint API Designer
AsyncAPI
Demo

12. 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
All contents © MuleSoft, LLC
1
3
4
5
6
7

13. Prerequisite
s
All contents © MuleSoft, LLC
● 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

14. Securing the End to End Traffic
All contents © MuleSoft, LLC

15. Q&A

16. Mani Rautroy
Integration Architect
mrautroy@xtivia.com
Bill Marcial
Director of Enterprise Architecture
wmarcial@xtivia.com
Robert Ralston
Sr. Business Development Manager
rralston@xtivia.com
Chaitanya Kumar Narvaneni
Director, Application Development
cnarvaneni@xtivia.com

17. Quiz

18. Q1: Select all that are specific and unique for an NGINX based
Ingress Resource Template
1. Multiple ingress configurations per application
2. TLS and HTTPS configuration
3. Rewrite annotation to do path rewriting
4. URL parameter placeholders

19. Q2: How can you monitor the logs of MuleSoft application pods inside
of a kubernetes cluster. Select all that apply
1. Kubernetes pod writes log to stdout. Use ‘kubectl logs’ to view
logs
2. You can forward logs to Anypoint Monitoring provided you
have a Titanium subscription
3. Use OpsCentre for monitoring the pod logs
4. Use Splunk for Kubernetes to forward logs and visualize

20. Q3: Which of the following configurations are customers responsible for
when adopting Runtime Fabric on Self-Managed Kubernetes?(Select all
that apply)
1. Ingress controller
2. External log forwarding
3. Runtime Fabric agent
4. All of the above

21. Thank you