Hello CloudMakers!

⛱️ Summer is here, bringing with it longer days, clear blue skies, and hopefully, some well-deserved relaxation. Yet, even as we embrace the warmth of the new season, our thirst for knowledge and progress never takes a vacation. That's why we continue to delve into the ever-evolving world of Cloud and DevOps 😅

In the midst of barbecues, beach outings, and beautiful sunsets, today we shall see:

• a practical overview on Architecture Decision Records (ADR)

• validating best practices programmatically with HardenEKS

• is Podman a drop-in replacement for Docker?

Enjoy!

A practical overview on Architecture Decision Records (ADR)

As our digital infrastructures become increasingly complex, documenting the "why" behind our decisions becomes crucial.

This article emphasizes how ADRs act as guiding stars in the vast universe of software architecture. They don't just map out our technological choices but also offer rich context, providing insights into the reasons that shaped these decisions. A well-documented ADR serves as a knowledge reservoir for existing teams and an invaluable onboarding tool for newcomers.

HardenEKS: Validating Best Practices For Amazon EKS Clusters Programmatically

As we navigate the ever-evolving landscape of Amazon Elastic Kubernetes Service (EKS), a valuable tool has emerged: HardenEKS. This open-source, Python-based CLI, introduced in November 2022, has swiftly caught the attention of AWS teams and customers alike.

This article delves into how this tool systematically implements the guidelines outlined in AWS' EKS Best Practices Guide (EBPG) into a set of practical rules. Today, it integrates over 40 automated controls, continually expanding its scope to streamline your EKS operations.

What sets HardenEKS apart is its no-installation-required approach. Validating best practices against your EKS cluster externally, it provides a less intrusive means of compliance, suited for all experience levels.

Is Podman a Drop-in Replacement for Docker?

This article explores the practicality of Podman as a drop-in replacement for Docker. Podman, like Docker, is a container engine, but it operates without a daemon and by default, runs containers as rootless, enhancing security.

The piece challenges Podman's claim of being a straightforward Docker substitute by examining the process of building and running a production-ready Dockerfile for a Spring Boot application. The investigation includes running single and multiple containers, enabling inter-container communication, and checking how volumes can be mounted, all using Podman commands as one would use Docker.

Thank you for reading my newsletter!

If you liked it, please invite your friends to subscribe!

If you were forwarded this newsletter and liked it, you can subscribe for free here:

Have you read an article you liked and want to share it? Send it to me and you might see it published in this newsletter!

Interested in old issues? You can find them here!