You're reading from Secure Continuous Delivery on Google Cloud Implement an automated and secure software delivery pipeline on Google Cloud using native services

Product type Paperback

Published in Apr 2024

Publisher Packt

ISBN-13 9781805129288

Length 304 pages

Edition 1st Edition

Languages

Tools

Kubernetes

Concepts

Continuous Delivery

Authors (3):

Nathaniel Avery

David Dorbin

Giovanni Galloro

View More author details

Table of Contents (19) Chapters

Preface

1. Part 1:Introduction and Code Your Application

2. Chapter 1: Introducing Continuous Delivery and Software Supply Chain Security FREE CHAPTER

3. Chapter 2: Using Skaffold for Development, Build, and Deploy

4. Chapter 3: Developing and Testing with Cloud Code

5. Chapter 4: Securing Your Code with Cloud Workstations

6. Part 2: Build and Package Your Application

7. Chapter 5: Automating Continuous Integration with Cloud Build

8. Chapter 6: Securely Store Your Software on Artifact Registry

9. Part 3: Deploy and Run Your Application

10. Chapter 7: Exploring Runtimes – GKE, GKE Enterprise, and Cloud Run

11. Chapter 8: Automating Software Delivery Using Cloud Deploy

12. Chapter 9: Securing Your Runtimes with Binary Authorization

13. Part 4: Hands-On Secure Pipeline Delivery and Looking Forward

14. Chapter 10: Demonstrating an End-to-End Software Delivery Pipeline

15. Chapter 11: Integrating with Your Organization’s Workflows

16. Chapter 12: Diving into Best Practices and Trends in Continuous Delivery

17. Index

Why subscribe?

18. Other Books You May Enjoy

Using a deployment strategy

Cloud Deploy supports two deployment strategies for GKE, Cloud Run, and GKE Enterprise:

Standard: This is the default strategy. It deploys the new or changed application into the target runtime, fully replacing any previous version.
Canary: This strategy incrementally deploys the changed application into the target runtime, gradually replacing the old version with the new one by configured percentages. This can be by the percentage of traffic or by the percentage of GKE pods.

In this section, we’ll configure and run a simple canary that replaces the old version with the new, first by 50%, then fully. The manifest we created at the beginning of this chapter specifies four replicas. The first phase of this canary will split them so that two replicas are running the old version and two are running the new version. Then, the last phase (which is always the stable phase) will deploy the new version to all four replicas.