Book Image

Google Cloud for DevOps Engineers

By : Sandeep Madamanchi
Book Image

Google Cloud for DevOps Engineers

By: Sandeep Madamanchi

Overview of this book

DevOps is a set of practices that help remove barriers between developers and system administrators, and is implemented by Google through site reliability engineering (SRE). With the help of this book, you'll explore the evolution of DevOps and SRE, before delving into SRE technical practices such as SLA, SLO, SLI, and error budgets that are critical to building reliable software faster and balance new feature deployment with system reliability. You'll then explore SRE cultural practices such as incident management and being on-call, and learn the building blocks to form SRE teams. The second part of the book focuses on Google Cloud services to implement DevOps via continuous integration and continuous delivery (CI/CD). You'll learn how to add source code via Cloud Source Repositories, build code to create deployment artifacts via Cloud Build, and push it to Container Registry. Moving on, you'll understand the need for container orchestration via Kubernetes, comprehend Kubernetes essentials, apply via Google Kubernetes Engine (GKE), and secure the GKE cluster. Finally, you'll explore Cloud Operations to monitor, alert, debug, trace, and profile deployed applications. By the end of this SRE book, you'll be well-versed with the key concepts necessary for gaining Professional Cloud DevOps Engineer certification with the help of mock tests.
Table of Contents (17 chapters)
1
Section 1: Site Reliability Engineering – A Prescriptive Way to Implement DevOps
6
Section 2: Google Cloud Services to Implement DevOps via CI/CD
Appendix: Getting Ready for Professional Cloud DevOps Engineer Certification

Points to remember

The following are some important points to remember:

  • Cloud Monitoring is a GCP service that collects metrics, events, and metadata from multi-cloud and hybrid infrastructures in real time.
  • A workspace provides a single pane of glass related to GCP resources.
  • A workspace can monitor resources from multiple monitored projects.
  • A monitored project, however, can only be associated with a single workspace.
  • Dashboards provide a graphical representation of key signal data, called metrics, in a manner that is suitable for end users or the operations team.
  • Metrics represent numerical measurements of resource usage that can be observed and collected across the system at regular time intervals.
  • MQL can be used to create a chart with a text-based interface and uses an expressive query language to execute complex queries against time series data.
  • Uptime checks test the availability of an external facing service within a specific timeout interval...