Skip to main content
this document is for:

Deployment: Invicti Platform on-premises

Update using Helm

Keeping your Invicti Platform on-premises installation up to date ensures you always have the latest features, security fixes, and performance improvements.

warning

After making any changes to your values.yaml file, you must apply them by running the helm upgrade command. This applies to all configuration updates, including changes to web_application_host, SMTP settings, or TLS certificates.

Update command

To update an existing installation, run the following command on the machine where Invicti is installed:

helm upgrade invicti-platform oci://platform-registry.invicti.com/invicti-platform-helm-charts/onpremises  --namespace invicti  --values ./values.yaml  --wait  --wait-for-jobs
tip

Add --debug for more detailed output. This can help troubleshoot installation issues.

Command explanation

  • helm upgrade invicti-platform - Upgrades the existing Helm release named invicti-platform.
  • oci://platform-registry.invicti.com/invicti-platform-helm-charts/onpremises - Specifies the location of the Invicti Platform Helm chart in the Invicti container registry.
  • --namespace invicti - Ensures the upgrade applies to the correct Kubernetes namespace.
  • --create-namespace - Creates the namespace if it doesn't already exist. If the namespace already exists, this flag has no effect.
  • --values ./values.yaml - Applies configuration from the values.yaml file. This file should contain all necessary deployment settings, including any customizations.
  • --wait - Instructs Helm to wait until all Kubernetes resources are fully ready before marking the upgrade as successful.
  • --wait-for-jobs- Ensures Helm also waits for Kubernetes Jobs (such as database schema migrations) to complete before finishing the upgrade.

Optional:

  • --reset-then-reuse-values - Keeps your current configuration but resets and applies defaults for any new values added in the latest chart version.
  • Use the --reset-then-reuse-values flag to ensure your configuration remains compatible with new chart defaults.
  • Use --cleanup-on-fail option if you want Helm to automatically remove any newly created resources if the upgrade fails. This flag helps prevent partial or inconsistent deployments when an upgrade does not complete successfully.

You can always override the default values using the --set option. Use --help for more information.

warning

Ensure you have cluster admin permissions before running the update. The script updates components in place, so downtime may occur during the process.

Verification

After the update, confirm that all services are running correctly:

kubectl get pods -n invicti

All pods should be in the running/completed state.

Terminal showing all pods in the running state.


Need help?

Invicti Support team is ready to provide you with technical help. Go to Help Center

Was this page useful?