
Installing Optimizer Hub on MicroK8s
MicroK8s can be used for testing, evaluating, and non-cloud-managed blob storage use of Optimizer Hub.
Make sure your MicroK8s meets the 18 vCore minimum for running Optimizer Hub. Although MicroK8s can run on multiple platforms, Optimizer Hub is only available for the x64 platform, so not on macOS with M-processor.
Installing MicroK8s
Install MicroK8s for your platform following this installation guide.
-
Install MicroK8s on Linux with Snap:
sudo snap install microk8s --classic -
Check the status while Kubernetes starts:
$ microk8s status --wait-ready microk8s is running high-availability: no datastore master nodes: 127.0.0.1:19001 datastore standby nodes: none -
Turn on the services you need, in our case, only
dashboard
:microk8s enable dashboard -
Access the Kubernetes dashboard:
$ microk8s dashboard-proxy Checking if Dashboard is running. Infer repository core for addon dashboard Waiting for Dashboard to come up. Trying to get token from microk8s-dashboard-token Waiting for secret token (attempt 0) Dashboard will be available at https://127.0.0.1:10443 Use the following token to login: eyJhbGciOiJSUzI1NiIs... -
You can now open the dashboard in the browser, using the token you got in the previous step.
Installing Optimizer Hub
Optimizer Hub uses Helm as the deployment manifest package manager. There is no need to manually edit any Kubernetes deployment manifests.
-
Make sure your Helm version is
v3.8.0
or newer, check it withhelm version
. -
Add the Azul Helm repository to your Helm environment:
microk8s helm repo add opthub-helm https://azulsystems.github.io/opthub-helm-charts/ microk8s helm repo update -
Create a namespace (i.e.
my-opthub
) for Optimizer Hub.microk8s kubectl create namespace my-opthub -
Clone or download the files from the GitHub opthub-helm-charts repository.
git clone https://github.com/AzulSystems/opthub-helm-charts.git -
Create a directory for your configuration files
mkdir ~/my-opthub/ -
Create MinIO storage:
-
Copy minio-dev.yaml and replace
minio-dev
withmy-opthub
or the namespace you created in the previous step.cp ~/opthub-helm-charts/minio-dev.yaml ~/my-opthub/minio-dev.yaml sed -i 's/minio-dev/my-opthub/g' ~/my-opthub/minio-dev.yaml # `-i` modifies the original file # `s/old/new/g`: s = substitute, g = all occurrences -
Copy minio-setup-job.yaml and again replace
minio-dev
.cp ~/opthub-helm-charts/minio-setup-job.yaml ~/my-opthub/minio-setup-job.yaml sed -i 's/minio-dev/my-opthub/g' ~/my-opthub/minio-setup-job.yaml -
Install the S3 compatible storage with:
microk8s kubectl apply -f ~/my-opthub/minio-dev.yaml -f ~/my-opthub/minio-setup-job.yaml
-
-
Create a configuration file
values-minikube.yaml
, based on the example file, to disable all resource definitions.cp ~/opthub-helm-charts/values-minikube.yaml ~/my-opthub/values-minikube.yaml -
Install using Helm, passing in the
values-minikube.yaml
. In case you don’t want to install the full Optimizer Hub, but only a part of the services, first check "Configuring the Active Optimizer Hub Services".microk8s helm install opthub opthub-helm/azul-opthub -n my-opthub -f ~/my-opthub/values-minikube.yamlThe command should produce output similar to this:
NAME: opthub LAST DEPLOYED: Tue Jun 17 16:52:18 2025 NAMESPACE: my-opthub STATUS: deployed REVISION: 1 TEST SUITE: None -
Verify that all started pods are ready:
$ microk8s kubectl get all -n my-opthub NAME READY STATUS RESTARTS AGE pod/cache-0 1/1 Running 0 2m58s pod/compile-broker-59b99b66d6-njmwg 1/1 Running 0 2m58s pod/gateway-8445f9d959-zvp5f 1/1 Running 0 2m58s pod/gw-proxy-6c7b66bb6f-t4675 1/1 Running 0 2m58s pod/minio 1/1 Running 0 3m42s pod/minio-setup-job-hqpw7 0/1 Completed 1 3m42s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/cache ClusterIP None <none> 5701/TCP 2m58s service/compile-broker ClusterIP 10.152.183.188 <none> 50051/TCP 2m58s service/gateway LoadBalancer 10.152.183.250 <pending> 50051:31401/TCP 2m58s service/gateway-headless ClusterIP None <none> 50051/TCP 2m58s service/minio ClusterIP 10.152.183.157 <none> 9000/TCP,9090/TCP 3m42s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/compile-broker 1/1 1 1 2m58s deployment.apps/gateway 1/1 1 1 2m58s deployment.apps/gw-proxy 1/1 1 1 2m58s NAME DESIRED CURRENT READY AGE replicaset.apps/compile-broker-59b99b66d6 1 1 1 2m58s replicaset.apps/gateway-8445f9d959 1 1 1 2m58s replicaset.apps/gw-proxy-6c7b66bb6f 1 1 1 2m58s NAME READY AGE statefulset.apps/cache 1/1 2m58s NAME STATUS COMPLETIONS DURATION AGE job.batch/minio-setup-job Complete 1/1 12s 3m42s -
You can also verify the status on the dashboard we opened before, by selecting the
my-opthub
namespace in the header:
Upgrade Optimizer Hub on MicroK8s
You can upgrade your Optimizer Hub instance running on MicroK8s, and keep all profile data and compile caches as the S3 compatible minio storage won’t be upgraded.
-
List the currently installed version:
$ microk8s helm list --namespace my-opthub NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION opthub my-opthub 1 2025-06-17 16:59:26.33115804 +0200 CEST deployed azul-opthub-1.11.2 1.11.2 -
List the available versions on the helm repo:
$ microk8s helm repo update $ microk8s helm search repo opthub-helm --versions NAME CHART VERSION APP VERSION DESCRIPTION opthub-helm/azul-opthub 1.11.2 1.11.2 Azul Intelligence Cloud: Optimizer Hub opthub-helm/azul-opthub 1.11.1 1.11.1 Azul Intelligence Cloud: Optimizer Hub opthub-helm/azul-opthub 1.11.0 1.11.0 Azul Intelligence Cloud: Optimizer Hub opthub-helm/azul-opthub 1.10.2 1.10.2 Azul Intelligence Cloud: Optimizer Hub opthub-helm/azul-opthub 1.10.1 1.10.1 Azul Intelligence Cloud: Optimizer Hub opthub-helm/azul-opthub 1.10.0 1.10.0 Azul Intelligence Cloud: Optimizer Hub opthub-helm/azul-opthub 1.9.5 1.9.5 Azul Intelligence Cloud: Optimizer Hub ... -
Upgrade and use the same settings and files from the installation, just by replacing
install
withupgrade
:microk8s helm upgrade opthub opthub-helm/azul-opthub -n my-opthub -f ~/my-opthub/values-minikube.yamlNoteTo upgrade or downgrade to a specific version, add --version <version>
. -
After upgrading, verify the version with the helm list command again.
-
You can check the version of the MinIO storage with this command:
$ microk8s kubectl exec -n my-opthub pod/minio -- minio --version minio version RELEASE.2024-12-18T13-15-44Z (commit-id=16f8cf1c52f0a77eeb8f7565aaf7f7df12454583)