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. Docker images use a layered model – true or false?
  2. You can delete an image from a server if a container using that image is already running – true or false?
  3. How do you remove a running container from a server? (Multiple answers are possible)

    a. docker rm <container_id>

    b. docker rm -f <container_id>

    c. docker stop <container_id> && docker rm <container_id>

    d. docker stop -f <container_id>

  4. Which of the following options are container build best practices? (Multiple answers are possible)

    a. Always add layers that don't frequently change at the beginning of the Dockerfile

    b. Combine multiple steps into a single directive to reduce layers

    c. Only use the required files in the container to keep it lightweight and reduce the attack surface

    d. Use semantic versioning in your Docker tags and avoid the latest version

    e. It is a best practice to include package managers and a shell within the container as it helps...