Visit Azul.com Support

Platform-Specific Installation Steps

Table of Contents
Need help?
Schedule a consultation with an Azul performance expert.
Contact Us

AWS EKS

If you are using Amazon Web Services, you can simplify the process of starting and maintaining your cluster considerably by using the Elastic Kubernetes Service (EKS).

Please download opthub-install-25.11.0.zip for additional files to configure Optimizer Hub on AWS EKS.

Cluster Requirements

You can create a cluster following the steps in Cluster Provisioning on EKS, or use a cluster created by any other means according to these requirements:

  • ReadyNow Orchestrator requires on-demand EC2 instances. Don’t use spot instances.

  • All the nodes must have at least 8 vCores and 32 GB RAM to fit the Optimizer Hub pods.

  • The suggested EC2 instance types are m6 or m7. Using instances with less powerful CPUs may negatively impact the performance of Optimizer Hub.

Cluster Provisioning on EKS

If you don’t have a cluster available to run Optimzer Hub, you can provision one on EKS with the following steps:

  1. Install and configure the eksctl and aws command-line tools.

    If you don’t have permissions to set up networking components, have your administrator create the Virtual Public Cloud.

  2. In the downloaded package, navigate to the eks directory.

  3. In opthub_eks.yaml, replace the placeholders {your-cluster-name}, {your-region}, and {path-to-your-key} with the correct values.

  4. If you are working with an existing VPC and do not want eksctl to create one, uncomment the vpc section and replace {your-vpc} and {your-subnet} with the correct values.

  5. Pass the modified opthub_eks.yaml file to eksctl to create the cluster. For more information, look at the eskctl config file schema. Apply the file with the following command:

     
    eksctl create cluster -f opthub_eks.yaml

    This command takes several minutes to execute, and when successful ends with the following output:

     
    [✔] EKS cluster "eks-opthub-cluster" in "eu-central-1" region is ready

By using opthub_eks.yaml, the following gets created in your AWS account:

  • CloudFormation stacks for the main EKS cluster and each of the NodeGroups in the cluster.

  • A Virtual Private Cloud called eksctl-{cluster-name}-cluster/VPC. If you chose to use an existing VPC, this is not created. You can explore the VPC and its related networking components in the AWS VPC console. The VPC has all of the required networking components configured:

    • A set of three public subnets and three private subnets

    • An Internet Gateway

    • Route Tables for each of the subnets

    • An Elastic IP Address for the cluster

    • A NAT Gateway

  • An EKS Cluster, including four nodegroups with one m5.2xlarge instance provisioned:

    • infra - For running Grafana and Prometheus.

    • opthubinfra - For running the Optimizer Hub infrastructure components.

    • opthubcache - For running the Optimizer Hub cache.

    • opthubserver - For running the Optimizer Hub compile broker settings.

  • IAM artifacts for the Autoscaling Groups:

    • Roles for the Autoscaler groups for the cluster and for each subnet

    • Policies for the EKS autoscaler

Install Optimizer Hub on an EKS Cluster

Follow the installation instructions on Standard Optimizer Hub Installation Procedure on Kubernetes to install all services of Optimizer Hub. Or, in case you don’t want to install the full Optimizer Hub but only a part of the services, check Installing Optimizer Hub without Cloud Native Compiler.

In the step where you use Helm to create the node groups in the cluster, pass in the additional configuration file eks/values-eks.yaml, located in the installation package. This file includes the nodegroup affinity settings and other settings expected by EKS.

The Helm installation command needs to be extended with the values-eks.yaml config file:

 
helm install opthub opthub-helm/azul-opthub \
  -n my-opthub \
  -f values-eks.yaml \
  -f values-override.yaml

When adding multiple `values files, remember the last one takes precedence.

Microsoft Azure

Google Cloud Platform

Other Kubernetes Platform