A Cloud Deploy execution environment is the environment in which Cloud Deploy executes its render, predeploy, deploy, verify, and postdeploy operations. The execution environment consists of the following components:
The Cloud Build worker pool (default or private) in which Cloud Deploy executes render, predeploy, deploy, verify, and postdeploy operations
The service account (default or alternate) that calls Cloud Deploy to perform these actions
The storage location (default or alternate) for rendered manifests in Cloud Storage
The Cloud Build timeout for operations (default or custom)
This document describes the default execution environment, service accounts, and storage for Cloud Deploy, as well as why and how you can change these defaults.
Defaults
The following are the defaults that Cloud Deploy uses to run, to execute rendering and deployment, and to store assets such as rendered manifests:
Default worker pool
By default, Cloud Deploy runs in the default Cloud Build worker pool. However, you can configure Cloud Deploy to use a Cloud Build private worker pool.
For more details about worker pools, see the Cloud Build Overview of default pools and private pools.
Default execution service account
By default, Cloud Deploy uses the default Compute Engine service account.
Default Cloud Deploy storage location
This value is the Cloud Storage bucket where Cloud Deploy stores your rendered manifests. By default, Cloud Deploy creates a Cloud Storage bucket, in the same region as the Cloud Deploy resources, taking the following form:
<location>.deploy-artifacts.<project ID>.appspot.comDefault Cloud Build timeout
By default, Cloud Build has a timeout of 1 hour on operations it performs for Cloud Deploy. You can change that timeout in the execution environment specification in target configuration.
Default verbosity for Skaffold, gcloud CLI, and kubectl