Upgrading Cloud Native Compiler

Table of Contents

Upgrading from CNC 1.2 or Earlier
Upgrading 1.3 or Later

Need help?

Schedule a consultation with an Azul performance expert.

Plain upgrades only incur a few seconds of downtime while the gateway pod is restarted. The cluster performs a rolling update on all other components without incurring downtime on the client VMs. However, pre-helm releases will need to be re-installed.

Upgrading from CNC 1.2 or Earlier

In Cloud Native Compiler 1.3, the installation process changed to use Helm charts. To upgrade a pre-1.3 release, uninstall CNC and install again using the Helm charts. The easiest way is to uninstall by removing the original CNC namespace:
```
 $ kubectl delete namespace compiler
```

Upgrading 1.3 or Later

Refer to changelog for any changes that might affect configuration.
Update the helm repository (this will refresh package information):
```
 $ helm repo update
```
Perform helm upgrade
```
 $ helm upgrade compiler cnc-helm/prime-cnc -n compiler -f values-override.yaml
```
If you are targeting a specific version, use the --version <target version> flag. Depending on where you are installing, do not forget to add any further values files you may be using, e.g. values-eks.yaml using further -f <values file> clauses. It is necessary to keep all values you used with the original installation unless told otherwise.
Verify that all started pods are ready:
```
 $ kubectl get all -n compiler
```