Book Image

Modern DevOps Practices

By : Gaurav Agarwal
Book Image

Modern DevOps Practices

By: Gaurav Agarwal

Overview of this book

Containers have entirely changed how developers and end-users see applications as a whole. With this book, you'll learn all about containers, their architecture and benefits, and how to implement them within your development lifecycle. You'll discover how you can transition from the traditional world of virtual machines and adopt modern ways of using DevOps to ship a package of software continuously. Starting with a quick refresher on the core concepts of containers, you'll move on to study the architectural concepts to implement modern ways of application development. You'll cover topics around Docker, Kubernetes, Ansible, Terraform, Packer, and other similar tools that will help you to build a base. As you advance, the book covers the core elements of cloud integration (AWS ECS, GKE, and other CaaS services), continuous integration, and continuous delivery (GitHub actions, Jenkins, and Spinnaker) to help you understand the essence of container management and delivery. The later sections of the book will take you through container pipeline security and GitOps (Flux CD and Terraform). By the end of this DevOps book, you'll have learned best practices for automating your development lifecycle and making the most of containers, infrastructure automation, and CaaS, and be ready to develop applications using modern tools and techniques.
Table of Contents (19 chapters)
1
Section 1: Container Fundamentals and Best Practices
7
Section 2: Delivering Containers
15
Section 3: Modern DevOps with GitOps

Questions

  1. Which of the following are CI tools? (Multiple answers are possible)

    a. Jenkins

    b. GitHub Actions

    c. Kubernetes

    d. AWS Cloudbuild

  2. It is a best practice to configure post-commit triggers – True/False?
  3. Jenkins is a SaaS-based CI tool – True/False?
  4. Kaniko requires Docker to build your containers – True/False?
  5. Jenkins agents are required for which of the following reasons? (Multiple answers are possible)

    a. They make builds more scalable.

    b. They help offload the management function from the Jenkins master.

    c. They allow for parallel builds.

    d. They keep the Jenkins master less busy.

  6. AWS Cloudbuild does not have an out-of-the-box build trigger solution – True/False?
  7. Which of the following is required for a scalable Jenkins server as described in the example? (Multiple answers are possible)

    a. Kubernetes cluster

    b. Jenkins master node

    c. Jenkins agent node

    d. Credentials to interact with the container registry.