Kuma Meshes Part I - The basics - A tutorial

How it works, what we can monitor with it and why is it
different
By João Esperancinha (2024/03/31)

Who am I?
Overview
Understanding the problems
Project objective
Target audience
Market trends
Cycle diagram
João Esperancinha
● Java
● Kotlin
● Groovy
● Scala
● Software Engineer 10+ years
● JESPROTECH owner for 1 year
● Kong Champion
● Java Professional
● Spring Professional

Intro - What is Kuma?
Kuma is a platform agnostic
open-source control plane for
service mesh and microservices
management, with support for
Kubernetes, VM, and bare metal
environments.
https://kuma.io/docs/2.6.x/introduction/overview-of-kuma/

Chapter I
Getting the services
up and running

Step 1
Our application
Chapter I
https://github.com/jesperancinha/wild-life-safety-monitor

Chapter I - Our Application
Albatross pictureby chrispearson72 Flickr stream CC BY 2.0 DEED / https://nl.wikipedia.org/wiki/Albatrossen#/media/Bestand:Black_Browed_Albatross_gnd.jpg

Step 2
Installing all
commands
Chapter I

What do we need in general
1
A cluster to get our pods running.
This will be achieved with kind.
(kubernetes in docker)
3
A way to manage and configure our pods.
This will be achieved with kubectl
2
A local registry that we can access inside
our deployment environment.
This will be achieved with kind
4
A command to allow Kuma to install the
environment and inject the sidecars.
This will be achieved with kumactl.

Step 3
Creating
a Cluster
Chapter I

kind create cluster --name=wlsm-mesh-zone
kubectl cluster-info --context kind-wlsm-mesh-zone
Creating a Cluster

helm repo add kuma https://kumahq.github.io/charts
helm repo update
helm upgrade -i kuma kuma/kuma
helm install --create-namespace --namespace kuma-system kuma kuma/kuma
Creating a Cluster - Control Plane GUI

Step 4
Creating a
local docker
registry
Chapter I

./kind-with-registry.sh
Creating a local docker registry

docker build . --tag localhost:5001/wlsm-listener-service;
docker push localhost:5001/wlsm-listener-service;
Creating a local docker registry

Step 5
Going
through
the code
Chapter I

spring.r2dbc.url=r2dbc:postgresql://wlsm-database-deployment.wlsm-namespace.svc.cluster.local:5432/wlsm
Going through the code
wslm.url.collector=http://wlsm-collector-deployment.wlsm-namespace.svc.cluster.local:8081/api/v1/collector
Listener Service
Collector Service

Step 6
Making
the deploy
scripts
Chapter I

apiVersion: v1
kind: Namespace
metadata:
name: wlsm-namespace
labels:
kuma.io/sidecar-injection: enabled
---
Making the deploy scripts
---
apiVersion: v1
kind: Service
metadata:
name: wlsm-listener-deployment
spec:
selector:
app: wlsm-listener
ports:
- protocol: TCP
appProtocol: http
port: 8080
apiVersion: apps/v1
kind: Deployment
metadata:
name: wlsm-listener
namespace: wlsm-namespace
spec:
replicas: 1
selector:
matchLabels:
app: wlsm-listener
template:
metadata:
labels:
app: wlsm-listener
spec:
containers:
- name: wlsm-listener-service
image: localhost:5001/wlsm-listener-service:latest
imagePullPolicy: Always
ports:
- containerPort: 8080

Step 7
Running
the application
Chapter I

Running the application
kubectl apply -f listener-deployment.yaml --force;

Chapter II
Exploring
Kuma features

Chapter II - Exploring Kuma features
MeshTrafficPermission
echo "apiVersion: kuma.io/v1alpha1
kind: MeshTrafficPermission
metadata:
namespace: kuma-system
name: mtp
spec:
targetRef:
kind: Mesh
from:
- targetRef:
kind: Mesh
default:
action: Allow" | kubectl apply -f -

Mesh
echo "apiVersion: kuma.io/v1alpha1
kind: Mesh
metadata:
name: default
spec:
mtls:
enabledBackend: ca-1
backends:
- name: ca-1
type: builtin" | kubectl apply -f -

MeshTrafficPermission (Deny)
apiVersion: kuma.io/v1alpha1
metadata:
name: mtp
spec:
targetRef:
kind: Mesh
from:
- targetRef:
kind: Mesh
default:
action: Deny" | kubectl apply -f -

MeshTrafficPermission (Specific)
echo "
metadata:
name: wlsm-database
spec:
targetRef:
kind: MeshService
name: wlsm-database-deployment_wlsm-namespace_svc_5432
from:
- targetRef:
kind: MeshService
name: wlsm-collector-deployment_wlsm-namespace_svc_8081
default:
action: Allow" | kubectl apply -f -

MeshFaultInjection (Specific)
echo "
kind: MeshFaultInjection
metadata:
name: default
labels:
kuma.io/mesh: default # optional, defaults to `default` if it isn't configured
spec:
targetRef:
kind: MeshService
name: wlsm-collector-deployment_wlsm-namespace_svc_8081
from:
- targetRef:
kind: MeshService
name: wlsm-listener-deployment_wlsm-namespace_svc_8080
default:
http:
- abort:
httpStatus: 500
percentage: 50" | kubectl apply -f -

● Source Repository
○ https://github.com/jesperancinha/wild-life-safety-monitor
Use git clone from the command prompt to download the full code base:
> git clone https://github.com/jesperancinha/wild-life-safety-monitor.git
You’ll be prompted for a username and password which should be your github account.
The easy way:
> make b
> make run
The manual way:
> gradle build
> ./gradlew run
Project Location

Resources:
● K9s
● https://support.konghq.com/support/s/article/How-to-enable-debug-logging-for-kuma-sidecar-without-
using-port-forward
● https://spacelift.io/blog/kubectl-logs
● https://docs.konghq.com/mesh/latest/policies/meshtrafficpermission/
● https://kuma.io/features/

Kuma Meshes Part I - The basics - A tutorial

More Related Content

Similar to Kuma Meshes Part I - The basics - A tutorial (20)

More from João Esperancinha (17)

Recently uploaded (20)

Kuma Meshes Part I - The basics - A tutorial