Maintained with ☕️ by
IcePanel logo

(Cloud Composer 3) New metrics are available for Cloud Composer 3 environments

Share

Services

## Feature _(Cloud Composer 3)_ [New metrics](https://cloud.google.com/composer/docs/composer-3/monitor-environments#services-quotas) are available for Cloud Composer 3 environments: * CPU quota limit for Cloud Composer workloads * CPU quota usage for Cloud Composer workloads ## Feature _(Cloud Composer 3)_ You can now use custom certificates when [installing packages from your private repository](https://cloud.google.com/composer/docs/composer-3/install-python-dependencies#install-private-repo). This change is gradually rolled out to all Cloud Composer 3 environments. To obtain this change earlier, upgrade the Airflow build of your environment. ## Issue The issue with automatic environment upgrades and upgrading Airflow builds in Cloud Composer 3 **is resolved** and these operations are working. If you think that your environment is still impacted by this issue, please reach out to the Cloud Support team. ## Change _(New Cloud Composer 2 environments only)_ Cloud Composer 2 environments in versions 2.10.2 and later **always use the environment's service account** for performing PyPI packages installations. This change applies **only to newly created environments**, existing environments that are upgraded to 2.10.2 and later versions will not get this change. ## Change _(Cloud Composer 3 only)_ The `/data` folder is now synchronized with Airflow triggerers. ## Change _(Available without upgrading)_ Improved the error message generated when the Cloud Composer Service Agent service account is missing permissions on the project or on the environment's service account. ## Fix _(Cloud Composer 2)_ Cloud Composer 2 environments that use PSC interfaces will no longer try to allocate IP ranges for VPC peerings in the tenant project. Environments that use PSC instead of VPC peerings do not use these ranges. This fixes a problem where these ranges overlapped with ranges used for the PSC subnetwork. ## Change The Redis persistent disk is now automatically deleted together with the environment. This persistent disk is used by the Redis queue and stores only technical data. ## Fix Fixed an issue where the user-defined Cloud DNS configuration for Google API domains would break Cloud Composer 3 environment creation and attachment of VPC networks. ## Change The `worker_autoscale` Airflow configuration option is blocked in Cloud Composer 2\. Previously, it was blocked only in Cloud Composer 3. ## Fix Fixed a problem with the interpolation of pip.conf file. Now the pip.conf file is not interpolated and can contain unescaped % characters. ## Fix Removed the warning log message about in-memory storage because it doesn't apply to Cloud Composer. ## Change The `importlib-resources` package was removed from preinstalled packages. ## Change New [Airflow builds](https://cloud.google.com/composer/docs/concepts/versioning/composer-versions#images-composer-3) are available in Cloud Composer 3: * composer-3-airflow-2.10.2-build.5 (default) * composer-3-airflow-2.9.3-build.12 ## Change New [images](https://cloud.google.com/composer/docs/concepts/versioning/composer-versions#images-composer-2) are available in Cloud Composer 2: * composer-2.10.2-airflow-2.10.2 (default) * composer-2.10.2-airflow-2.9.3 ## Change Cloud Composer 2.10.1 is a version with an extended upgrade timeline. ## Deprecate Cloud Composer version 2.5.4 has reached its [end of support period](https://cloud.google.com/composer/docs/concepts/versioning/composer-versioning-overview#version-deprecation-and-support).