This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

    Manual Upgrade (v2435)

    As of August 2020, Sysdig has changed its upgrade procedure.

    All on-premises installations and upgrades are now scheduled with and guided by Sysdig technical account managers and professional services division. See Oversight Services Now Offered for All Installs and Upgrades .

    For customers, the instructions in this section are for review purposes only.

    Sysdig platform on-premise releases are listed here. Each release has a version number and specific Release Notes.

    Sysdig On-Premise version 2435 replaces v2304, v2266, and v2172. Versions 2304 and 2266 are hotfix releases. Version 2172 is a major release.

    Sysdig On-Premise version 2435 includes the following changes:

    • Dashboards upgraded from v1 to v2: This update happens automatically.

      However, if you have saved v1 dashboards and need to reapply them, follow these instructions: Migrate Saved Dashboards from V1 to V2.

    • Architecture Change in the ContainersIn previous releases, there was a single backend container which ran several processes.

      As of version 2435, the processes have been divided into unique containers, following container best practices.

      As a result, it is necessary to apply the entire configuration, not simply change the image version. Follow the instructions below.

    Contents

    If you have licensed and will run only Sysdig Monitor, then you upgrade fewer components than if you also use Sysdig Secure, as described below.

    Download the New Version

    Use get to download the new version from Sysdig’s GitHub and unzip it.

    For example:

    wget https://github.com/draios/sysdigcloud-kubernetes/archive/<version_number>.tar.gz &&  tar xvf <version_number>.tar.gz
    

    Edit New Files to Match Your Customized Files

    Edit the following files within the sysdigcloud directory to match any customizations you may have made in your existing production system.

    config.yaml

    Edit the Sysdig user name, default user, API URL, Sysdig license, collector endpoint, from your config.yaml to the new config.yaml .

    sysdigcloud.default.user: test@sysdig.com
    collector.endpoint: onprem.sysdigcloud.com
    collector.port: "6443"
    api.url: https://onprem.sysdigcloud.com:443
    

    deployment YAML files

    Edit the CPU limits and replicas in the deployment YAML files: api-deployment.yaml, collector-deployment.yaml, worker-deployment.yaml

    Note that the values in the sample below are examples only; edit them to match the requirements of your deployment.

    spec:
     replicas: 1
    
    ....
    
    resources:
      limits:
        cpu: "4"
        memory: 4Gi
      requests:
        cpu: "1"
        memory: 1G
    

    Apply the Files

    Run the kubctl commands to apply the relevant files to the environment.

    This upgrade updates dashboards from v1 to v2. The process requires 20-30 minutes on large systems, and the environment remains live throughout the rolling upgrade.

    DO NOT create or delete dashboards during the upgrade.

    After upgrading, if you have saved v1 dashboards previously and need to upload them to the v2 environment, see Migrate Saved Dashboards from V1 to V2.

    Upgrade for Sysdig Monitor Only

    kubectl -n sysdigcloud apply -f config.yaml
    kubectl -n sysdigcloud apply -f api-deployment.yaml
    kubectl -n sysdigcloud apply -f collector-deployment.yaml
    kubectl -n sysdigcloud apply -f worker-deployment.yaml
    

    Upgrade for Sysdig Monitor + Sysdig Secure

    kubectl -n sysdigcloud apply -f config.yaml
    kubectl -n sysdigcloud apply -f api-deployment.yaml
    kubectl -n sysdigcloud apply -f collector-deployment.yaml
    kubectl -n sysdigcloud apply -f worker-deployment.yaml
    kubectl -n sysdigcloud apply -f scanning-api-deployment.yaml
    kubectl -n sysdigcloud apply -f scanning-alertmgr-deployment.yaml