Updating SystemLink Enterprise
- Updated2025-11-26
- 2 minute(s) read
Modify the configuration or upgrade to a newer version of the SystemLink Enterprise application.
You must have all configuration files when you upgrade. If part of the configuration is missing, upgrading might result in application failures and resource deletions from the cluster.
- A cluster administrator with full access rights.
- A user with a cluster role that includes privileges to create CustomResourceDefinitions, ClusterRoles, and ClusterRoleBindings.
-
To install prerequisites to the systemlink-admin namespace,
open the command prompt and run the following commands.
helm upgrade admin-release oci://downloads.artifacts.ni.com/ni-docker/ni/helm-charts/systemlinkadmin --install --version version --namespace admin-namespace --values systemlink-admin-values.yaml --values systemlink-values.yaml --values systemlink-secrets.yaml --wait --timeout 10m0s
Where,- admin-release is the release name used for installing the systemlink-admin Helm chart.
- downloads.artifacts.ni.com/ni-docker is replaced with the URL of the mirror registry if using a local mirror.
- version is the specific version of the software to install.
- admin-namespace is the namespace created for the systemlink-admin Helm chart.
-
To update the application, run the following commands.
helm upgrade release oci://downloads.artifacts.ni.com/ni-docker/ni/helm-charts/systemlink --install --version version --namespace namespace --values systemlink-values.yaml --values systemlink-secrets.yaml --set-file database.postgresCertificate=postgres.pem
Where,- release is the name Helm assigns to the installed collection of software.
- downloads.artifacts.ni.com/ni-docker is the URL of the registry. If using a local mirror, replace this URL with the URL of the mirror registry.
- version is the specific version of the software to install.
- namespace is the namespace created for the application.
The update command applies any changes you made to the values in your files since installing. If necessary, containers are updated to the specified version. Changes are applied using a rolling update strategy to avoid downtime.
Related Information
- Rolling Update Deployment
- Resolving RabbitMQ Cluster Incompatibility
Reset the RabbitMQ cluster if it fails to initialize properly due to an incompatible feature flag configuration. You might encounter this issue while updating SystemLink Enterprise.