Skip to content

Latest commit

 

History

History
57 lines (49 loc) · 3.35 KB

README.md

File metadata and controls

57 lines (49 loc) · 3.35 KB
Raw

Azul Cloud Native Compiler Helm Charts

Azul Cloud Native Compiler is a server-side optimization solution that offloads JIT compilation to separate and dedicated service resources, providing more processing power to JIT compilation while freeing your client JVMs from the burden of doing JIT compilation locally.

Cloud Native Compiler (CNC) is shipped as a Kubernetes cluster which you provision and run on your cloud or on-premise servers. You can install CNC on any Kubernetes cluster:

  • Kubernetes clusters that you manually configure with kubeadm
  • A single-node minikube cluster. You should run CNC on minikube only for evaluation purposes. Make sure your minicube meets the 18vCore minimum for running CNC.
  • Managed cloud Kubernetes services such as Amazon Web Services Elastic Kubernetes Service (EKS), Google Kubernetes Engine, and Microsoft Azure Managed Kubernetes Service.

See the Cloud Native Compiler Documentation for more information. Note: By downloading and using Cloud Native Installer you are agreeing to the Cloud Native Compiler Evaluation Agreement.

To install Cloud Native Compiler:

  1. Install Azul Zulu Prime version 21.09.01 or later on your client machine.
  2. Make sure your Helm version is v3.8.0 or later.
  3. Add the Azul Helm repository to your Helm environment:
helm repo add cnc-helm https://azulsystems.github.io/cnc-helm-charts/
helm repo update
  1. Create a namespace (i.e. compiler) for the CNC service.
kubectl create namespace compiler
  1. Create the values-override.yaml file in your local directory.
  2. If you have a custom cluster domain name, you will need to provide it:
clusterName: "example.org"

  1. Configure sizing and autoscaling of the CNC components according to the sizing guide. By default autoscaling is on and the CNC service can scale up to 10 Compile Brokers.

  2. If needed, configure external access in your cluster. If your JVMs are running within the same cluster as CNC, you can ignore this step. Otherwise, it is necessary to configure an external load balancer in values-override.yaml.
    For clusters running on AWS an example configuration file is available in this GitHub project.

  3. Install using Helm, passing in the values-override.yaml:

helm install compiler cnc-helm/prime-cnc -n compiler -f values-override.yaml

In case you need a specific CNC version, please use --version <version> flag. The command should produce output similar to this:

NAME: compiler
LAST DEPLOYED: Thu Apr  7 19:21:10 2022
NAMESPACE: compiler
STATUS: deployed
REVISION: 1
TEST SUITE: None

Advanced deployment without compilation feature.
If you want to deploy CNC without its compilation feature, add provided values-disable-compiler.yaml to your helm command:

helm install compiler cnc-helm/prime-cnc -n readynow-only -f values-override.yaml -f values-disable-compiler.yaml
  1. Verify that all started pods are ready:
kubectl get all -n compiler