Basic Upgrade (Replicated)
Support for new Replicated installations will be deprecated in the coming months. Feel free to contact Sysdig Support with questions.
Non-Airgapped Installation
Upgrading is very simple when your environment has access to the Internet during the installation process (non-airgapped).
It is highly recommended to follow upgrade best practices:
Keep upgrades current
Upgrade progressively without skipping versions, and
Test upgrades in a non-mission-critical or staging environment before rolling in to production.
Review the On-Premises Upgrades for supported upgrade paths.
Upgrade Replicated Components
Check Current Version
The Replicated infrastructure installs its own container based agents
that deploy and manage the various Sysdig back-end components. To
confirm the currently running version of the Replicated agent, perform
replicated --version
at the command line on each host. [Reference
Replicated.com]
Upgrade Replicated Client
Log in to the Replicated Management Console and stop the Sysdig application (Sysdig Monitor and Sysdig Secure, if applicable) before upgrading the Replicated client.
Run the following command on the management host to upgrade the replicated infrastructure:
sudo curl -sSL https://get.replicated.com/docker | sudo bash
Run the following command on the remaining nodes in the cluster:
sudo curl -sSL https://get.replicated.com/operator | sudo bash
Upgrade Sysdig Application
Installation Sequence:
Pre-Version 860: Install upgrades sequentially, one version at a time.
Version 860 - 1091: You can directly install the version you want.*
Version 1091 - Sept 2018 release: All users must upgrade from 1091 - Sept 2018 and run the Unified Events migration tool.
Version 2266: See Note, below.
*Sequential installs (even when not strictly required) ensure consistent database migrations and allow for easier troubleshooting, should problems occur. Sysdig recommends staying fairly up-to-date on the release cycle to avoid “stacking up” upgrades.
Log in to the
Replicated Management Console > Dashboards
.Click
View Update
.The release history is listed, and “New” for any new releases.
Click
Install
for the desired release.
Upgrades to version 2304
After upgrading to version 2304, you must add a node for emailrenderer
and nginxfrontend
to the replicated cluster, and then run a command on
the node.

Private and Public IP Addresses: Provide the IPs where the containers will run.
Select emailrenderer and nginxfrontend.
Run the
curl
command as noted in the image above, including the optional parameters as needed for your environment.
Airgapped Installation
Upgrade Replicated Components
Check Current Version
The Replicated infrastructure installs its own container based agents
that deploy and manage the various Sysdig back-end components. To
confirm the currently running version of the Replicated agent, perform
replicated --version
at the command line on each host. See also
Replicated.com.
Upgrade Replicated Client
Download the latest Replicated agent installation package:
curl https://s3.amazonaws.com/replicated-airgap-work/replicated.tar.gz > replicated.tar.gz
In a command shell, extract the Replicated installer:
sudo tar xzvf replicated.tar.gz
Run the ‘install.sh’ script on the management host:
sudo cat ./install.sh | sudo bash -s airgap
Run the ‘operator_install.sh’ script on all remaining nodes:
sudo cat ./operator_install.sh | sudo bash -s airgap
Upgrade Sysdig Application
Download the new Sysdig application .
airgap
installer, using the link and password supplied for the initial installation.Copy the .
airgap
file to the update directory on the management host.To check or configure the update path, log in to the Replicated Management Console and click
Console Settings > Airgapped Settings
section under the gear icon.In the Replicated Management Console, select the
Dashboard
tab and clickCheck Now
.Click
Install
for the desired version.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.