Steps and Commands for RTF Installation on self managed kubernetes

Command Line Tools Installation:

Pre-requisites

1. JDK 

OpenJDK 11 > https://adoptium.net/temurin/releases/?version=11

OpenJDK 8 > https://adoptium.net/temurin/releases/?version=8

2. Install Chocolatey on Windows 

a. Run a Powershell terminal as Administrator, then run Get-ExecutionPolicy. If it returns Restricted, then run Set-ExecutionPolicy AllSigned or Set-ExecutionPolicy Bypass -Scope Process.

b. Install the Chocolatey Package Manager, a.k.a `choco`:

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString(‘https://community.chocolatey.org/install.ps1’))

3. Install kubectl

choco install kubernetes-cli –version=1.24.10 –allow-downgrade -y

4. Install rtfctl

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

5. Install Azure CLI MSI

https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli

Validate all tools are installed :

• kubectl version –client –short 
• rtfctl version –help
• az

Azure KS Commands (Creating Kubernetes Cluster): 

Create a resource group in Azure.

1. CREATE CLUSTER

az aks create –resource-group <<resourcegroup>> –name <<clustername>> –node-count 2 –generate-ssh-keys –kubernetes-version 1.24.9 –node-vm-size Standard_DS2_v2

2. Check created clusters

az aks list

3. GET CREDS (Get access credentials for a managed kubernetes cluster)

az aks get-credentials –resource-group <<resourcegroup>> –name <<clustername>>

4. View Kubernetes config

kubectl config view

5. Test connection to your cluster

kubectl get services

6. GET NODES:

kubectl get nodes

Create Runtime Fabric Configuration in Runtime Manager

AND Get the Activation Code

RTF requires a separate license, so make sure you have a valid license

1.ACTIVATION CODE: 

<<activation code>>

2.Validate the activation code:

rtfctl validate <<activation code>>

Examine existing components in Kubernetes cluster before RTF installation

3. Install the RTF:

rtfctl install <<activation code>>

 

4. Check the RTF Status:

rtfctl status

Now your RTF status should be activated in Runtime Manager

Apply associated Environment (as per requirement)

Insert Mule License Key

1.Encode Mule license key

Powershell command to encode the license

$BASE64_ENCODED_LICENSE=[convert]::ToBase64String((Get-Content -path “license.lic” -Encoding byte))

2.set /p encoded_text=<mulel.txt   (In directory where encoded license present)

3.$encoded_text = Get-Content -Path “mulel.txt” -Raw (Run this command in Powershell)

4.rtfctl apply mule-license %encoded_text%

Now If you go to “Inbound Traffic”, you will see a Warning.

We need to configure Ingress in order to enable inbound traffic to our RTF cluster.

Define a custom ingress configuration

1. kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.0/deploy/static/provider/cloud/deploy.yaml

CREATE INGRESS CONTROLLER:

kubectl apply -f ingress-resource.yaml

After configuring the ingress you will see the base endpoint as following:

Verify domains configured as base endpoints to runtime fabric

Deploy a Mule Application

12. After deploying app to check the namespace of mule apps

kubectl get namespace

13. To check services running on rtf

kubectl get services -n <<namespace>>

14. To check pods running

kubectl get pods -n <<namespace>>

15. GET EXTERNAL IPs:

kubectl get ingress -n <<namespace>>

16. APPLICATION CALL: