Installer Upgrade (3.5.0-3.5.1)
As of version 3.5.0/3.5.1, 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.
With version 3.5.0, both installing and upgrading with the installer has
been simplified from previous versions. Upgrade differs from Install in
that you run an
installer diff to discover the differences between the
old and new versions and then installer deploy for the new version.
Some guidance from Sysdig Support may be warranted in highly customized installations.
Upgrading is performed just like a fresh install, with the addition of
generate diff step. Refer to the appropriate workflow, depending
on your environment:
Postgres Version Update v10.x to 12.x
Version 3.5.0 upgrade includes an automatic Postgres version upgrade. Depending on the size of your database, that can take some time.
The data migration takes approximately 1 min per 1 GiB of data. The speed of data migration ultimately depends on the underlying storage media.
To complete the Postgres upgrade, you must also ensure there is sufficient disk space in the volume when using a local-disk storage provisioner in Kubernetes. For example, if your current Postgres size is 100 GiB, ensure there is at least another 100 GiB space free in the volume. This is required temporarily for copying the data during the upgrade.
3.5.0 - 3.5.1 Elasticsearch Upgrade
Upgrading from version 3.5.0 to 3.5.1 also upgrades Elasticsearch. Due
to the Elasticsearch update strategy of
ondelete, the pods will only
be upgraded when they are restarted:
image: quay.io/sysdig/elasticsearch:220.127.116.11 image: quay.io/sysdig/elasticsearch:18.104.22.168
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.