Visit Azul.com Support

Installing Optimizer Hub

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

Optimizer Hub is shipped as a Kubernetes cluster which you provision and run on your cloud or on-premise servers.

Supported Platforms

Optimizer Hub is available for x64 platforms only, however, supports connections from Zing JVMs running on both x86 and ARM 64-bit machines.

Load Balancing

It’s recommended to use a load balancer or service mesh to set up a high-availability system, optionally with a secondary fallback system. JVMs connecting to Optimizer Hub need a stable, single entry point to communicate with the service.

It’s recommended to use your own load balancer and configure the DNS of the system that must be used by the JVMs to connect. See Configuring Optimizer Hub Host > Using your Own Load Balancer and the Readiness (healthy) API. If no load balancer is available, you can use the optional gw-proxy, included in Optimizer Hub.

Benefits of a Load Balancer

A load balancer provides this external access point while also potentially offering benefits like:

  • SSL configuration in the load balancer

  • Traffic distribution across Optimizer Hub components

  • High availability

  • Network isolation

  • Consistent endpoint for clients regardless of internal pod IP changes

Load Balancer Requirements

  • The load balancer must be an application-level load balancer, i.e., it must understand the gRPC protocol (which is built on top of HTTP/2) and load balance each gRPC request independently.

  • The load balancer may not limit the duration of gRPC calls. Optimizer Hub uses streaming gRPC calls, which can last for hours, days, or how long the VM stays alive. These long-lived calls may not be considered as an error and may not be killed.

Supported Kubernetes Environments

You can install Optimizer Hub on any Kubernetes cluster:

Note
 By downloading and using Optimizer Hub, you agree with the Azul Platform Prime Evaluation Agreement.