On-Premises Upgrades
This section describes how to upgrade an on-premise installation, depending on whether it was installed using a Kubernetes or a Replicated orchestrator.
As needed, version-specific upgrade or migration instructions will be added to this section.
Oversight Services Now Offered for All Installs and Upgrades
As part of our continued focus on our customers, we are now offering oversight services for all on-premise installs and upgrades. Your Technical Account Manager (TAM), in conjunction with our support organization and Professional Services [where applicable], will work with you to:
Assess your environment to ensure it is configured correctly
Review your infrastructure to validate the appropriate storage capacities are available
Review and provide recommendations for backing up your Sysdig data
Work with you to ensure our teams are ready to assist you during the install and upgrade process
Provide the software for the install
Be available during the process to ensure a successful deployment
You can always review the process in the documentation on GitHub (v. 3.6.0+) or the standard docs site (for older versions).
If you are a new customer looking to explore Sysdig, please head over here to sign up for a trial on our SaaS Platform. Alternatively, you can contact us here.
Explore the Upgrade Topics
This section provides roadmaps for upgrading Sysdig Platform components. Review the topics appropriate to your environment.
| Topics | Description |
|---|---|
| Supported Upgrade Paths | Understand the upgrade and migration paths for on-prem installations. |
| Installer Upgrade (3.5.0-3.5.1) | Upgrading Sysdig Platform to v 3.5.0 from v. 3.0, 3.2.x using the installer tool. There is no manual install option as of version 3.5.0. |
| Installer Upgrade (2.5.0+) | Upgrading Sysdig Platform v2.5.0 - 3.2.2 by using the Installer tool. As of version 2.5.0, the Sysdig platform on Kubernetes or OpenShift should be upgraded using the Installer tool. |
| Manual Upgrade (3.0.0+) | Upgrading Sysdig Platform v3.0.0 and above manually on Kubernetes. |
| Upgrading v2.4.1- v2.5.0 on Kubernetes | Upgrading the Sysdig Platform versions between 2.4.1and 2.5.0 manually on Kubernetes. |
| Upgrading v2.3.0 on Kubernetes | Upgrading Sysdig Platform v2.3.0 manually on Kubernetes. |
| Upgrading v2435 on Kubernetes | Upgrading Sysdig Platform v2435 manually on Kubernetes. |
| Basic Upgrade on Replicated | Upgrading the mandatory components of the Sysdig Platform on a Replicated environment. |
Supported Migration Paths
In general, Sysdig tests and supports direct upgrade from five releases back to the current version. Release-specific requirements are listed in the table below.
For Kubernetes Environments
Install Version | Incl. Hotfixes | Supported Upgrade From | Notes | Baseline Documentation |
|---|---|---|---|---|
3.6.0 (by request) | 3.2.2, 3.5.1 | Platform changes: new inline scanner version, interactive session expiration. Sysdig Secure modules added/changed, including Compliance, Event Forwarding, Capture improvements, Image Scan results. Sysdig Monitor improvements in UI. | ||
3.5.1 (by request) | 3.0, 3.2.x, (3.5.0 if it was installed) | New/changed modules in both Sysdig Secure and Sysdig Monitor, including: New Getting Started and Overview, new Dashboards, overhauled Secure Events Feed, new navigation bar icons and layout, changed Image scanning navigation and usage, new Secure vulnerability feed and benchmark test, | Installer Upgrade (3.5.0-3.5.1) with oversite assistance from Sysdig Support | |
2.5.0, 3.2.0 | Hot fix | |||
3.2.1, 3.2.2 | 2.5.0, 3.0.0 | In Sysdig Secure: Data retention limits for scan results, vulnerabiity comparison in scan results, redesigned Captures page, RBAC capability, activity audit improvement. In Sysdig Monitor and Secure: S3-compatible storage for Capture files. | ||
2.4.1, 2.5.0 | Beta Activity Audit feature, Beta Policy Advisor feature. | |||
2.3.0, 2.4.1 | New Installer tool for upgrading; new documentation site; inline scanning for Secure, other enhancements | |||
2.3.0 | Report service added; upgrade to Anchore license required | |||
1929, 2435 | Ability to secure Elasticsearch and the Cassandra DB with password authentication or SSL/TLS protection. | |||
(2304) (2266) (2172) | 1929, 1765 | Architecture changes to Dashboards & API pods. | Note that this replaces 2172, 2266, and 2304. | |
legacy | ||||
Migration Tool (MySQL Connector) Architecture & Port 443 change | legacy | |||
((1586) | legacy | |||
(1472) (1402) | legacy | |||
legacy | ||||
Migration Tool (Unified Events) | legacy | |||
legacy |
For Replicated Environments
Most Replicated environments can be upgraded directly to the current version. See also: Basic Upgrade (Replicated).
It is recommended to follow upgrade best practices:
- Keep upgrades current.
- Test upgrades in a non-mission-critical or staging environment before rolling into production.
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.