Upgrade On-Premises License

On-premises environments might require a license upgrade to renew, extend an expiration date, enable new features, add a service, or change the number of licensed agents. You can upgrade licenses manually or automatically.

After a license expires, there is a 14 day grace period before the agents disconnect. Make sure to renew the license to avoid any disruption.

Prerequisites

When you upgrade, whether manually or with the update-license command, ensure you update your values.yaml with the new license to prevent redeploying the Sysdig application with an old license in the future.

If you don’t update values.yaml and run the installer next time, say for an upgrade, the application will be redeployed with the old license.

Make sure that all the records you hold are updated with the latest license to prevent any license mismatch.

Version 7.x.x or 6.x.x

Automatic Upgrade

  1. Do one of the following options.

    • Pass the license from a file:
      installer update-license --license-file license.txt --namespace <YOUR-NAMESPACE>
    • Pass the license as a string:
      installer update-license --license <license-string> --namespace <YOUR-NAMESPACE>

    Replace <YOUR-NAMESPACE> with the namespace where your Sysdig application is installed.

Automatic Upgrade Using installer deploy

Optionally, you can use the installer deploy method explained in Automatic Upgrade in Version 5.x.x.

Manual Upgrade

  1. Update the license in all the applicable secrets:

    • sysdigcloud-api-secret
    • sysdigcloud-collector-secrets
    • sysdigcloud-streamsnap-secret
    • sysdigcloud-anchore-secret
    • sysdigcloud-worker-secret

  2. (Optional) If scanning v2 engine is enabled, update the license in the following ConfigMaps:

    • sysdigcloud-scanningv2-pkgmeta-api-config
    • sysdigcloud-scanningv2-vulns-api-config

  3. Restart the applicable deployments:

    • sysdigcloud-api

    • sysdigcloud-collector

    • sysdigcloud-streamsnap

    • sysdigcloud-worker

    • sysdigcloud-scanningv2-pkgmeta-api

    • sysdigcloud-scanningv2-vulns-api

    • sysdigcloud-anchore-core

    • sysdigcloud-anchore-policy-engine

    • sysdigcloud-anchore-api

    • sysdigcloud-anchore-catalog

    For example:

    kubectl rollout restart deployment \
sysdigcloud-api \
sysdigcloud-collector \
sysdigcloud-worker \
sysdigcloud-streamsnap \
sysdigcloud-scanningv2-pkgmeta-api \
sysdigcloud-scanningv2-vulns-api \
sysdigcloud-anchore-core \
sysdigcloud-anchore-policy-engine \
sysdigcloud-anchore-api \
sysdigcloud-anchore-catalog \
-n sysdigcloud

Version 5.x.x

Automatic Upgrade

The license file is simply entered as a configuration parameter in the values.yaml file. To apply the new license, update the values.yaml file with the new license, and run the installer.

  1. Open the values.yaml file.

  2. Specify your license as follows:

    sysdig:
  license: <replace_with_your_license>

  3. Run the following:

    ./installer deploy

Manual Upgrade

  1. Update the ConfigMap for sysdigcloud-config.

    # Required: Sysdig Cloud license
  sysdigcloud.license: "<replace_with_your_license>"

  2. Restart the Sysdig API, Worker, and Collector pods.

  3. (Optional) Restart the Anchore pods.

    For example:

    kubectl rollout restart deployment \
sysdigcloud-api \
sysdigcloud-collector \
sysdigcloud-worker \
sysdigcloud-anchore-core \
sysdigcloud-anchore-policy-engine \
sysdigcloud-anchore-api \
sysdigcloud-anchore-catalog \
-n sysdigcloud

Learn More