...
| Note |
|---|
|
- Kubernetes cluster (for more information, refer to https://kubernetes.io/):
- 1 virtual machine used as the control plane node and 3 nodes used as worker nodes
| Warning |
|---|
The names of worker nodes must match their FQDN. |
- Control plane node: 4 CPU cores, 8GB RAM
- Worker node: 16 CPU cores, at least 64GB RAM (depends on your deployment size)
- Kubernetes version: v1.28 or later
- Container runtime: Containerd (for more information, refer to https://containerd.io/)
- CNI: Calico
- Load Balancer: MetalLB (the configuration instructions are provided later in this chapter)
| Warning |
|---|
Most cloud providers do not support MetalLB. |
- IP: 1 additional IP address with the DNS A record that points to this IP (IP from your network that is not used by your cluster nodes).
- Ingress: ingress-nginx (with sticky session support).
| Info |
|---|
| Note that there are two nginx ingresses: ingress-nginx is maintained by the Kubernetes community, while nginx-ingress is maintained by F5 inc. The free F5 inc. version of nginx-ingress does not support “sticky sessions” which are required. Therefore, make sure you use ingress-nginx. |
- A Host with Docker or Podman to build images and push them to the image registry.
- An image registry (repository) such as Harbor, Sonatype Nexus, Gitlab, or Docker registry server to push and pull the images you will build.
- The applications needed to run Magic Collaboration Studio and services:
|
The following figure displays the environment used in this deployment example.
...
