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:

  • IC: In charge of the incident response, designates responsibilities and optionally takes on roles that were not designated, such as CL.
  • OL: Deals with resolving or handling the incident – technical and tactical; executes the action plan by working with a Primary and Secondary Responder.
  • CL: The public face of incident response; responsible for communicating to all the stakeholders.
  • PL: Tracks system changes, identifies long-term changes by filing bugs, and arranges hand-offs. 
  • Command post: Refers to a meeting room or Slack channel where communication happens.
  • Live incident state document: Maintained by the CL about the incident and updates, and is later used for the postmortem.
  • An incident or outage should be called if specific expertise is needed, if the outage is visible, or if the issue is not resolved after an hour or so of effort.
  • Factors to overcome in order...