Upgrade environments

Cloud Composer 1 | Cloud Composer 2

Preview — Upgrading environments

This feature is covered by the Pre-GA Offerings Terms of the Google Cloud Terms of Service. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the launch stage descriptions.

This page describes how to upgrade your environment to a new Cloud Composer or Airflow version.

About upgrade operations

When you change the version of Airflow or Cloud Composer used by your environment, your environment upgrades.

Upgrading does not change how you connect to the resources in your environment, such as the URL of your environment's bucket, or Airflow web server.

During an upgrade, Cloud Composer:

1. Re-deploys your environment's components using new versions of Cloud Composer images.
2. Applies Airflow configuration changes, such as custom PyPI packages or Airflow configuration option overrides, if your environment had them before the upgrade.
3. Updates the Airflow airflow_db connection to point to the new Cloud SQL database.

Before you begin

Caution: Before you upgrade, make sure that you know the differences between the current versions of Airflow and Cloud Composer and the versions that you are upgrading to. Incompatible changes can cause your DAGs to no longer work. For more information, see Release Notes and versioning overview.

• Upgrading is currently in Preview. Use this feature with caution in production environments.

• You cannot downgrade to an earlier version of Cloud Composer or Airflow.

• You can upgrade the Cloud Composer version, the Airflow version, or both at the same time.

• You can only upgrade to the latest Cloud Composer version within the same major version.

• It is not possible to upgrade to a different major version of Cloud Composer or Airflow in-place. You can manually transfer DAGs and configuration between environments. For more information, see:

  • Migrate from Cloud Composer 1, Airflow 1 to Cloud Composer 2, Airflow 2.
  • Migrate from Cloud Composer 1, Airflow 2 to Cloud Composer 2, Airflow 2.
  • Migrate from Cloud Composer 1, Airflow 1 to Cloud Composer 1, Airflow 2.

• You must have a role that can trigger environment upgrade operations. In addition, the service account of the environment must have a role that has enough permissions to perform upgrade operations. For more information, see Access control.

• For the list of PyPI packages in a version that you want to upgrade to, see the list of Cloud Composer versions.

• You cannot upgrade your environment if the Airflow database contains more than 16 GB of data. During an upgrade, a warning is shown if the Airflow database size is more than 16 GB. In this case, perform the database maintenance to reduce the database size.

• The image version that you upgrade to must support your environment's current Python version.

Caution: Do not upgrade GKE clusters of your Cloud Composer environments to newer versions. Use the GKE version that was pre-configured during the environment creation and rely on auto-upgrades of the GKE service.

Check that your environment is up to date

Cloud Composer displays warnings when your environment's image approaches its end of support date. You can use these warnings to always keep your environments in the full support period.

Figure 1. A deprecation message is displayed on the Environment details page

Cloud Composer keeps track of the Cloud Composer image version that your environment is based on. When the image approaches its end of support date, you can see a warning in the list of environments and on the Environment details page.

To check if your environment image is up to date:

Console

1. In Google Cloud console, go to the Environments page.

   Go to Environments

2. In the list of environments, click the name of your environment. The Environment details page opens.

3. Go to the Environment configuration tab.

4. In the Image version field, one of the following messages is displayed:

   • Newest available version. Your environment image is fully supported.

   • New version available. Your environment image is fully supported and you can upgrade it to a later version.

   • Support for this image version ends in... Your environment image approaches the end of the full support period.

   • This version is not supported as of... Your environment is past the full support period.

Note: You can always upgrade your environment to a later version, even if the environment is past the full support period.

View available upgrades

To view Cloud Composer versions that you can upgrade to:

Console

1. In Google Cloud console, go to the Environments page.

   Go to Environments

2. In the list of environments, click the name of your environment. The Environment details page opens.

3. Go to the Environment configuration tab and click Upgrade Image Version.

4. For the list of available versions, click the Cloud Composer Image version drop-down menu.

gcloud

gcloud beta composer environments list-upgrades \
  ENVIRONMENT_NAME \
  --location LOCATION

Replace:

• ENVIRONMENT_NAME with the name of the environment.
• LOCATION with the region where the environment is located.

Example:

gcloud beta composer environments list-upgrades example-environment \
  --location us-central1

API

You can view available versions for a location. To do so, construct an imageVersions.list API request.

For example:

// GET https://composer.googleapis.com/v1/projects/example-project/
// locations/us-central1/imageVersions

Checking for PyPI package conflicts before upgrading

Preview — Upgrade check

This feature is covered by the Pre-GA Offerings Terms of the Google Cloud Terms of Service. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the launch stage descriptions.

You can check if PyPI packages installed in your environment have any conflicts with preinstalled packages in the new Cloud Composer image.

A successful check means that there is no PyPI package dependency conflicts between the current and the specified version. Note that an upgrade operation might still not be successful because of other reasons.

Console

To run an upgrade check for your environment:

1. In Google Cloud console, go to the Environments page.

   Go to Environments

2. In the list of environments, click the name of your environment. The Environment details page opens.

3. Go to the Environment configuration tab, locate the Image version entry, and click Upgrade.

4. In the Environment version upgrade dialog, in the New version drop-down list, select a Cloud Composer version that you want to upgrade to.

5. In the PyPI packages compatibility section, click Check for conflicts.

6. Wait until the check is complete. If there are PyPI package dependency conflicts, then the displayed error messages contain details about conflicting packages and package versions.

gcloud

To run an upgrade check for your environment, run the environments check-upgrade command with the Cloud Composer image version that you want to upgrade to.

gcloud beta composer environments check-upgrade \
    ENVIRONMENT_NAME \
    --location LOCATION \
    --image-version COMPOSER_IMAGE

Replace:

• ENVIRONMENT_NAME with the name of the environment.
• LOCATION with the region where the environment is located.
• COMPOSER_IMAGE with the new Cloud Composer image version that you want to upgrade to, in the form composer-a.b.c-airflow-x.y.z.

Example:

gcloud beta composer environments check-upgrade example-environment \
  --location us-central1 \
  --image-version composer-1.18.9-airflow-1.10.15

Example output:

Waiting for [projects/example-project/locations/us-central1/environments/
example-environment] to be checked for PyPI package conflicts when upgrading
to composer-1.18.9-airflow-1.10.15. Operation [projects/example-project/locations/
us-central1/operations/04d0e8b2-...]...done.
...

Response:
'@type': type.googleapis.com/
google.cloud.orchestration.airflow.service.v1beta1.CheckUpgradeResponse
buildLogUri: https://console.cloud.google.com/cloud-build/builds/79738aa7-...
containsPypiModulesConflict: CONFLICT
pypiConflictBuildLogExtract: |-
The Cloud Build image build failed: Build failed; check build logs for
details. Full log can be found at https://console.cloud.google.com/
cloud-build/builds/79738aa7-...
Error details: tensorboard 2.2.2 has requirement
setuptools>=41.0.0, but you have setuptools 40.3.0.

As an alternative, you can run an upgrade check asynchronously. Use the --async argument to make an asynchronous call, then check the result with the gcloud composer operations describe command.

API

Construct an environments.checkUpgrade API request.

Specify the image version in the imageVersion field:

{
  "imageVersion": "COMPOSER_IMAGE"
}

Replace COMPOSER_IMAGE with the new Cloud Composer image version that you want to upgrade to, in the form composer-a.b.c-airflow-x.y.z.

Upgrade your environment

Caution: Pause all DAGs and wait for in-progress tasks to finish before upgrading.

To upgrade your environment to a later version of Cloud Composer or Airflow:

Console

1. In Google Cloud console, go to the Environments page.

   Go to Environments

2. In the list of environments, click the name of your environment. The Environment details page opens.

3. Go to the Environment configuration tab.

4. Locate the Image version item and click Upgrade.

5. From the Image version drop-down menu, select a version.

6. Click Upgrade.

gcloud

gcloud beta composer environments update \
  ENVIRONMENT_NAME \
  --location LOCATION \
  --image-version COMPOSER_IMAGE

Replace:

• ENVIRONMENT_NAME with the name of the environment.
• LOCATION with the region where the environment is located.
• COMPOSER_IMAGE with the new Cloud Composer image version that you want to upgrade to, in the form composer-a.b.c-airflow-x.y.z.

For example:

gcloud beta composer environments update
  example-environment \
  --location us-central1 \
  --image-version composer-1.18.9-airflow-1.10.15

API

1. Construct an environments.patch beta API request.

2. In this request:

   1. In the updateMask parameter, specify the config.softwareConfig.imageVersion mask.

   2. In the request body, in the imageVersion field, the new Cloud Composer image version that you want to upgrade to, in the form composer-a.b.c-airflow-x.y.z.

For example:

// PATCH https://composer.googleapis.com/v1beta1/projects/example-project/
// locations/us-central1/environments/example-environment?updateMask=
// config.softwareConfig.imageVersion

  {
    "config": {
      "softwareConfig": {
        "imageVersion": "composer-1.18.9-airflow-1.10.15"
      }
    }
  }

Terraform

Warning: If you specify a different major version of Airflow or Cloud Composer, Terraform deletes your environment and creates a new one. You can upgrade only within minor versions of Airflow or Cloud Composer.

The image_version field in the config.software_config block controls the Cloud Composer image of your environment. In this field, specify a new Cloud Composer image.

  resource "google_composer_environment" "example" {
  provider = google-beta
  name = "ENVIRONMENT_NAME"
  region = "LOCATION"

  config {
    software_config {
      image_version = "COMPOSER_IMAGE"
    }
  }
}

Replace:

• ENVIRONMENT_NAME with the name of the environment.
• LOCATION with the region where the environment is located.
• COMPOSER_IMAGE with the new Cloud Composer image version that you want to upgrade to, in the form composer-a.b.c-airflow-x.y.z.

Example:

resource "google_composer_environment" "example" {
  provider = google-beta
  name = "example-environment"
  region = "us-central1"

  config {
    software_config {
      image_version = "composer-1.18.9-airflow-1.10.15"
    }
  }
}

What's next

• List of Cloud Composer images
• Cloud Composer versioning
• Update environments