You're reading from Google Cloud for DevOps Engineers A practical guide to SRE and achieving Google's Professional Cloud DevOps Engineer certification

Product type Paperback

Published in Jul 2021

Publisher Packt

ISBN-13 9781839218019

Length 482 pages

Edition 1st Edition

Tools

Kubernetes

Concepts

DevOps

Author (1):

Sandeep Madamanchi

View More author details

Table of Contents (17) Chapters

Preface

1. Section 1: Site Reliability Engineering – A Prescriptive Way to Implement DevOps

2. Chapter 1: DevOps, SRE, and Google Cloud Services for CI/CD FREE CHAPTER

3. Chapter 2: SRE Technical Practices – Deep Dive

4. Chapter 3: Understanding Monitoring and Alerting to Target Reliability

5. Chapter 4: Building SRE Teams and Applying Cultural Practices

6. Section 2: Google Cloud Services to Implement DevOps via CI/CD

7. Chapter 5: Managing Source Code Using Cloud Source Repositories

8. Chapter 6: Building Code Using Cloud Build, and Pushing to Container Registry

9. Chapter 7: Understanding Kubernetes Essentials to Deploy Containerized Applications

10. Chapter 8: Understanding GKE Essentials to Deploy Containerized Applications

11. Chapter 9: Securing the Cluster Using GKE Security Constructs

12. Chapter 10: Exploring GCP Cloud Operations

13. Mock Exam 1

Answers

14. Mock Exam 2

15. Other Books You May Enjoy

Appendix: Getting Ready for Professional Cloud DevOps Engineer Certification

Chapter 2: SRE Technical Practices – Deep Dive

Reliability is the most critical feature of a service or a system and should be aligned with business objectives. This alignment should be tracked constantly, meaning that the alignment needs measurement. Site reliability engineering (SRE) prescribes specific technical tools or practices that will help in measuring characteristics that define and track reliability. These tools are service-level agreements (SLAs), service-level objectives (SLOs), service-level indicators (SLIs), and error budgets.

SLAs represent an external agreement with customers about the reliability of a service. SLAs should have consequences if violated (that is, the service doesn't meet the reliability expectations), and the consequences are often monetary in nature. To ensure SLAs are never violated, it is important to set thresholds. Setting these thresholds ensures that an incident is caught and potentially addressed before repeated occurrences of...