How to Setup MuleSoft Runtime Fabric on Self-Managed Kubernetes With AKS

Introduction

MuleSoft announced the general availability of Anypoint Runtime Fabric on Azure Kubernetes Service (AKS) and Amazon Elastic Kubernetes Service (EKS) with the v1.8 release. Release 1.8 allows two flavors of Runtime Fabric as follows:

  1. Runtime Fabric with Mule Appliance.
  2. Runtime Fabric with BYOK (Bring your Own Kubernetes).

RTF with Mule appliance is shipped with mule appliance and is packaged with its own Kubernetes. Therefore, it allows enterprises and implementing partners to take advantage of cutting-edge technologies such as Kubernetes and docker without knowing much about them. However, these days, most enterprises are moving towards the cloud and have embraced these technologies. 

Mule4 Automated Policy

Types of Mulesoft Policy


Support for Automated Policies

  • Automated policies are only available for Mule runtime engine (Mule4) APIs using a MuleSoft-hosted control plane.
  • All runtime deployment targets support automated policies (CloudHub, Runtime Fabric, and Hybrid).
  • Automated policies have priority over the same types of policies already applied to a specific API proxy.
  • As an administrator, we can apply policies specific to external identity providers (IdPs, such as OpenID) if the environment to which you want to apply policies includes them.

Steps to Apply Automated Policy

  • In the API Manager, select Automated Policies from the navigation menu on the left.
  • Click Apply new automated policy.
  • Select the provided policy that you want to configure.
  • Apply to a specific set of runtimes.
  • Click Apply.

Select Exchange Policy screenshot

RTF Log Forwarding Approaches to Graylog

Agenda 

  • Introduction.
  • MuleSoft RTF Platform.
  • About Graylog.
  • Runtime Fabric Log Forwarding Approaches To Graylog.

Introduction

  • RTF controls Mule runtimes in K8s executed docker containers called pods, all packaged with Gravity (Kubernetes cluster and all its applications into a single file called a "Cluster Image") for the expertise of installation and portability. 
  • A basic condition is to find a way to promote the Mule application logs to 3rd party logging platforms like Graylog to maintain the logs between redeployment or in the event of crashes.
  • Out of the box RTF log forwarding.
  • Third-party agent polling.
  • Hybrid (Unified way of logging where the customer is using both CloudHub as well as RTF).

MuleSoft RTF Platform

automated runtime

  • Anypoint platform is the main offering that has 2 main components. Management plane, and runtime plane. While creating individual containers while deploying the application in RTF, it keeps runtime independent from others and the same follows for continuous deployments.
  • As it builds an independent runtime container for each application which makes it to handle multi runtime version deployment. 
  • And discussing resource scaling, it supports both horizontal and vertical scaling by simple configuration or easier command to add more resources to existing infrastructure with zero downtime.
  • With its health monitoring and configuration persistence behavior, it adheres to escape from application failover. For instance, if any runtime goes out of service then it replicates another runtime instance to avoid platform failover.

About Graylog

Once messages are being received, it can be poked around and explore a bit. There are several pages available, though not all pages may be visible to all users, depending on individual permissions. The following are a few brief descriptions of each page’s purpose and function.