Kubernetes Requirements
Optimizer Hub is available for x64 platforms only, however, supports connections from Zing JVMs running on both x86 and ARM 64-bit machines.
Kubernetes Cluster
You can install Optimizer Hub on any Kubernetes cluster:
-
Kubernetes clusters that you manually configure with kubeadm:
-
Managed cloud Kubernetes services such as:
-
A single-node cluster:
|
Note
|
By downloading and using Optimizer Hub, you agree with the Azul Platform Prime Evaluation Agreement. |
Kubernetes Pods
You can find the default sizes for the pods in the values.yaml file that is part of the Helm chart:
-
Gateway: CPU 7, RAM 28GB
-
Compile Broker: CPU 7, RAM 28GB
-
Cache: CPU 7, RAM 28GB
-
gwProxy: CPU 7, RAM 1GB
-
Management Gateway: CPU 2, RAM 2GB
-
Operator: CPU 1, RAM 2GB
Requirements for ephemeral storage (temporary storage space allocated to Kubernetes pods that is non-persistent and exists only for the lifetime of the pod):
-
Compile Broker: 8GB
-
All other pods: 1GB
|
Note
|
Make sure to use the required number of CPUs, otherwise, this leads to reduced performance of the Optimizer Hub environment. |
Kubernetes Nodes
The underlying Kubernetes nodes (either cloud instances or physical computers) have to be large enough to fit one or more of the pods. This means they need to provide a multiple of 8 vCores with 4GB of RAM per vCore. For example: 8 vCore with 32GB, 16 vCores with 64GB, etc.
|
Note
|
Ensure the instances you run your Optimizer Hub have enough CPU to handle your requests. For example, on AWS use m6 and m7 instances, and on Google Cloud Platform c2-standard-8 instances.
|