Book Image

Modern DevOps Practices - Second Edition

By : Gaurav Agarwal
Book Image

Modern DevOps Practices - Second Edition

By: Gaurav Agarwal

Overview of this book

DevOps and the cloud have changed how we look at software development and operations like never before, leading to the rapid growth of various DevOps tools, techniques, and practices. This updated edition helps you pick up the right tools by providing you with everything you need to get started with your DevOps journey. The book begins by introducing you to modern cloud-native architecture, and then teaches you about the architectural concepts needed to implement the modern way of application development. The next set of chapters helps you get familiarized with Git, Docker, Kubernetes, Ansible, Terraform, Packer, and other similar tools to enable you to build a base. As you advance, you’ll explore the core elements of cloud integration—AWS ECS, GKE, and other CaaS services. The chapters also discuss GitOps, continuous integration, and continuous delivery—GitHub actions, Jenkins, and Argo CD—to help you understand the essence of modern app delivery. Later, you’ll operate your container app in production using a service mesh and apply AI in DevOps. Throughout the book, you’ll discover best practices for automating and managing your development lifecycle, infrastructure, containers, and more. By the end of this DevOps book, you'll be well-equipped to develop and operate applications using modern tools and techniques.
Table of Contents (24 chapters)
1
Part 1:Modern DevOps Fundamentals
6
Part 2:Container Orchestration and Serverless
10
Part 3:Managing Config and Infrastructure
14
Part 4:Delivering Applications with GitOps
18
Part 5:Operating Applications in Production

Questions

  1. Why should we constrain the provider version?
  2. You should always use the fmt and validate functions before a Terraform plan. (True/False)
  3. What does the Terraform plan command do? (Choose two)

    A. Refreshes the current state with the existing infrastructure state

    B. Gets the delta between the current configuration and the expected configuration

    C. Applies the configuration to the cloud

    D. Destroys the configuration in the cloud

  4. What does the terraform apply command do? (Choose three)

    A. Refreshes the current state with the existing infrastructure

    B. Gets the delta between the current configuration and the expected configuration

    C. Applies the configuration to the cloud

    D. Destroys the configuration in the cloud

  5. Why should you never store state files in source control? (Choose two)

    A. State files are plaintext, and therefore you expose sensitive information to unprivileged users.

    B. Source control does not support state locking, and therefore it might result in potential...