Upgrade from Chef Automate 1
This guide shows you how to upgrade your existing Chef Automate 1 installation to Chef Automate 2.
The Chef Automate upgrade process performs the following steps, in order:
- Runs preflight checks to ensure the system is suitable for Chef Automate 2, your Chef Automate 1 installation can be upgraded safely, and that the upgrade process will be able to migrate your data.
- Analyzes your Chef Automate 1 configuration files and migrates the relevant settings to a configuration file for Chef Automate 2. If incompatibilities are detected, the upgrade process fails and emits a description of the problem. You will have an opportunity to make any necessary changes to the generated Chef Automate 2 configuration.
- Downloads Automate 2. Chef Automate 2 is distributed via Habitat packages that are installed early in the process to minimize the downtime required for the upgrade.
- Puts your Chef Automate 1 installation into maintenance mode, waits for queued data to be processed, and then backs up all Chef Automate 1 data. This ensures that data will not be lost in the upgrade process and that you will be able to recover to a working state should an unforeseen error occur.
- Creates a local snapshot of Chef Automate 1 data for import into Chef Automate 2.
- Shuts down Chef Automate 1.
- Imports the Chef Automate 1 snapshot into Chef Automate 2.
- Starts Chef Automate 2. On startup, each component service of Chef Automate 2 detects imported data. Once all component services perform this step, Chef Automate 2 is ready to use and can accept new data.
- Migrates imported historical data in the background. You will be notified when the migration completes.
While we’ve taken care to make the upgrade process as smooth as possible, this section outlines some caveats to consider before you proceed.
Plan for Downtime
The Chef Automate 2 upgrade process puts your Chef Automate 1 installation into maintenance mode, shuts it down, and starts Chef Automate 2. During the downtime, the upgrade process takes a backup of your Chef Automate 1 data and exports some of its data to a local snapshot, which is imported into Chef Automate 2.
To minimize this downtime, we recommended that you take an online backup of Chef Automate 1 just prior to the upgrade. Historical information such as Chef Client run data and compliance scan data is backed up incrementally, which means that the upgrade only needs to transfer data that has been added since the last backup.
By default, the Chef Automate 2 upgrade process will not proceed if your Chef Automate 1 installation does not have backups configured. Invoke the upgrade using the
--skip-backup-check flag to avoid this check.
To configure Chef Automate 1 backups, see the Chef Automate 1 Documentation.
Unsupported Features and Topologies
Chef Automate 2 includes significant architectural and technical improvements to the core product platform. For the initial releases of this new major version, we do not yet support a handful of capabilities that were present in Chef Automate 1. If you rely on any of the capabilities listed below, we recommend you continue to use Chef Automate 1. Chef continues support of Chef Automate 1 while we develop upgrade paths for these capabilities on the new platform. For more information, please contact your Chef account representative.
- FIPS: Chef Automate 2 cannot currently operate in FIPS mode
- Disaster Recovery: Chef Automate 2 cannot currently operate in a primary/standby mode
- Workflow: Chef Automate 2 currently does not support Workflow
- Custom Kibana dashboards: Chef Automate 2 does not include Kibana in its technology stack
Should you wish to upgrade to Chef Automate 2 without these features, invoke the upgrade with the appropriate flags:
These flags enable you to upgrade by skipping preflight checks for unsupported features.
External Elasticsearch cluster
The Chef Automate 2 upgrade process requires manual intervention to upgrade a Chef Automate 1 installation that uses external Elasticsearch.
Automated upgrade for this configuration is in development. To upgrade an external Elasticsearch cluster, please reach out to a Customer Success or Customer Support representative for assistance.
New Data Paths
Chef Automate 2 stores its data in directories named
/hab/svc/$service-name/data. In particular:
- Elasticsearch data is stored in
- PostgreSQL data is stored in
If you use dedicated disks or partitions for either of these applications in Chef Automate 1, you must modify your disk mount configuration to make these disks/partitions available to Chef Automate 2.
Chef Automate 2 License
Login to Chef Automate to start a 60-day trial. The trial provides you with a 60-day license. Requesting a trial license requires internet connectivity in your Chef Automate 2 instance (only at the time of the license request).
If you are upgrading an airgapped Chef Automate installation, contact your Chef account representative for a Chef Automate 2 license.
Before you start the upgrade process, fulfill the requirements detailed in this section.
Command Line Tool
You will need the
chef-automate command line tool to initiate your upgrade.
Download the latest version of the Chef Automate CLI:
Unzip the package:
Move the unzipped
mv chef-automate /usr/local/bin
The Chef Automate upgrade process currently requires connectivity to the internet to install the Chef Automate 2 binaries. The standard Automate installation requires current versions for Chrome, Edge, or Firefox browsers. If you filter internet access via proxy or by other means, you must ensure the following domains are accessible:
The Chef Automate 2 installer respects the following environment variables:
If you use a proxy to manage outbound HTTP(S) connections, ensure these variables are set when running the upgrade.
Chef Automate 1 Version
Recent versions of Chef Automate 1 contain enhancements that the upgrade process relies upon to ensure your data is safely migrated. Currently, Chef Automate 1.8.38 or greater is required.
Chef Automate 2 requires the systemd init system. If you’re currently using Chef Automate 1 on an operating system that makes use of a different init system, we recommend consulting support for the appropriate upgrade strategy.
Upgrading an Airgapped Installation
On an internet-connected host, prepare an Airgap Installation Bundle. Transfer the Airgap
Installation Bundle and the
chef-automate command line tool to the airgapped host. Put
chef-automate command line tool in a directory that is in your $PATH, and proceed
with the upgrade process.
Backup your Chef Automate 1 install, to minimize the amount of data that will need to be backed up while the system is down:
Once the backup has completed, initiate the upgrade process. If your host is internet-connected, run the command:
chef-automate upgrade-from-v1 --channel current
If your host is airgapped, run the command:
chef-automate upgrade-from-v1 --airgap-bundle </path/to/bundle>
After the upgrader runs the preflight checks and analyzes your Chef Automate 1 configuration, it asks for confirmation to continue. Review the generated configuration file and if it is correct, type
yes to continue.
The upgrade process backs up your Chef Automate 1 data, shuts down Chef Automate 1, imports your data to Chef Automate 2, then starts Chef Automate 2. At this point, the upgrade process supplies you with a
automate-credentials.toml file containing new local login credentials for Chef Automate. Your LDAP configuration will migrate from Chef Automate 1. Historical data will be migrated in the background.