**Info:** These are the minimum system requirements for deploying Edge. If a custom microservice requires additional resources, you must configure the system accordingly in addition to the minimum requirements. For example, if a custom microservice requires 2 CPU cores and 4 GB of RAM, then the Kubernetes node must have 8 CPU cores (6 cores for standard workloads + 2 cores for your microservice) and 14 GB of RAM (10 GB for standard workloads + 4 GB for your microservice).
**Important:** MongoDB requires a CPU that supports AVX instructions. Ensure that the CPU type of the Kubernetes node supports AVX instructions. Use the command `sudo lscpu` to check whether the CPU supports AVX instructions.|
+|Hardware|CPU: 6 cores
RAM: 10 GB
CPU Architecture: x86-64
**Info:** If the Messaging Service is enabled (required for the microservice-based data broker and Notifications 2.0), the Kubernetes node must have an additional 2 CPU cores and 4 GB RAM.
**Info:** These are the minimum system requirements for deploying Edge. If a custom microservice requires additional resources, you must allocate them on top of the minimum requirements. For example, if a microservice needs 2 CPU cores and 4 GB RAM, the Kubernetes node must have an additional 2 CPU cores and 4 GB RAM.
**Important:** MongoDB requires a CPU that supports AVX instructions. Ensure that the CPU type of the Kubernetes node supports AVX instructions. Use the command `sudo lscpu` to check whether the CPU supports AVX instructions.|
|Kubernetes|Version 1.25.x has been tested (with potential compatibility for subsequent versions) and is supported across the following platforms:
- [Lightweight Kubernetes (K3s)](https://docs.k3s.io/installation). To enable the proper functioning of the Edge operator on K3s, you must install K3s with the following configuration options. For more information, see [Special instructions for K3s](/edge-kubernetes/installing-edge-on-k8/#special-instructions-for-k3s).
- [Kubernetes (K8s)](https://kubernetes.io/docs/setup/)
- [Amazon Elastic Kubernetes Service (EKS)](https://docs.aws.amazon.com/eks/latest/userguide/create-cluster.html)
- [Microsoft Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-portal?tabs=azure-cli)
**Info:** Edge on Kubernetes has undergone testing on the Kubernetes platforms mentioned above, using the Containerd, CRI-O, and Docker container runtimes. {{< c8y-admon-important >}} Edge on Kubernetes is tested and supported on single-node Kubernetes clusters. {{< /c8y-admon-important >}}| |Helm version 3.x|Refer to [Installing Helm](https://helm.sh/docs/intro/install/) for the installation instructions.| -|Disk space|Three static Persistent Volumes (PV) or a StorageClass configured with dynamic provisioning to bind.
- 75 GB for the Persistent Volume Claim (PVC) made for MongoDB (configurable through the Custom Resource).
- 10 GB for the Persistent Volume Claim (PVC) made for the Private Registry to host custom microservices.
- 5 GB for the Persistent Volume Claim (PVC) made for application logs.
- 75 GB for the Persistent Volume Claim (PVC) made for MongoDB (configurable through the Custom Resource).
- 10 GB for the Persistent Volume Claim (PVC) made for the Private Registry to host custom microservices.
- 5 GB for the Persistent Volume Claim (PVC) made for application logs.
If the Messaging Service is enabled (required for the microservice-based data broker and Notifications 2.0), an additional three static Persistent Volumes (PV) or a StorageClass configured with dynamic provisioning to bind, are required.
- 10 Gi for the Persistent Volume Claim (PVC) made for Pulsar Bookkeeper Ledgers.
- 2 Gi for the Persistent Volume Claim (PVC) made for Pulsar Bookkeeper Journal.
- 2 Gi for the Persistent Volume Claim (PVC) made for Pulsar Zookeeper.
- Your company name, under which the license has been bought
- The domain name (for example, myown.iot.com), where Edge will be reachable