Use Cloud Build to trigger a Spinnaker pipeline.

Use Cloud Pub/Sub to trigger a Spinnaker pipeline.

Use a custom builder in Cloud Build to trigger a Jenkins pipeline.

Use Cloud Pub/Sub to trigger a custom deployment service running in Google
Kubernetes Engine (GKE).

Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys
frequently

Inject the secret at the time of instance creation via an encrypted configuration
management system.

Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application

Leverage a continuous build pipeline that produces multiple versions of the secret for
each instance of the application.

Create a basic log filter matching userinfo, and then configure a log export in the Stackdriver console with Cloud Storage as a sink.

Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, and then copy the entries to a Cloud Storage bucket.

Create an advanced log filter matching userinfo, configure a log export in the Stackdriver console with Cloud Storage as a sink, and then configure a tog exclusion with userinfo as a
filter.

Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing
userinfo, create an advanced log filter matching userinfo, and then configure a log export in
the Stackdriver console with Cloud Storage as a sink.

Import the Stackdriver Profiler package, and configure it to relay function timing data to Stackdriver for further analysis.

Import the Stackdriver Debugger package, and configure the application to emit debug messages with timing information.

Instrument the code using a timing library, and publish the metrics via a health check endpoint that is scraped by Stackdriver.

Install an Application Performance Monitoring (APM) tool in both locations, and
configure an export to a central data storage location for analysis.

Adjust the SLO targets to be achievable by the service so you can bring it into
production.

Notify the development team that they will have to provide production support for the
service.

Identify recommended reliability improvements to the service to be completed before
handover.

Bring the service into production with no SLOs and build them when you have collected
operational data.

Use Cloud Storage to cache intermediate artifacts.

Run multiple Jenkins agents to parallelize the build.

Use multiple smaller build steps to minimize execution time.

Use larger Cloud Build virtual machines (VMs) by using the machine-type option.

In the Google Cloud Platform Console, use the Cost Breakdown section to visualize the costs per system.

Assign all instances a label specific to the system they run. Configure BigQuery billing
export and query costs per label.

Enrich all instances with metadata specific to the system they run. Configure Stackdriver
Logging to export to BigQuery, and query costs based on the metadata.

Name each virtual machine (VM) after the system it runs. Set up a usage report export
to a Cloud Storage bucket. Configure the bucket as a source in BigQuery to query costs
based on VM name.

A. Make the service’s SLO more strict.

B. Increase the service’s deployment velocity and/or risk.

C. Shift engineering time to other services that need more reliability.

Get the product team to prioritize reliability work over new features.

Change the implementation of your Service Level Indicators (SLIs) to increase
coverage.