Binarly Transparency Platform is upgraded by updating the chart version, everything else is handled by the underlying controller. This documentation details how to upgrade Binarly Transparency Platform using three popular methods of deployment to Kubernetes: ArgoCD, FluxCD, and Helm.
This documentation will also detail breaking change updates to the chart that require values changes or special instructions.
Rollback is not supported for stateful components and databases should be backed up before attempting to upgrade.
ArgoCD
ArgoCD will deploy the version detailed in the targetRevision field. Updating this field will trigger an update in ArgoCD:
FluxCD
FluxCD will deploy the version detailed in the version field of the HelmRelease. Updating this field will trigger a reconciliation:
Helm
Helm will deploy the version detailed in the chart reference. Changing the version in the reference and re-running the command will upgrade the release.
CRDs are not upgraded by Helm when using --skip-crds. Apply the CRDs from the new chart version before upgrading the application.
First apply the CRDs for the new version:
then upgrade the application: