Chapter 11. PaC and Infrastructure as Code
We spent the last several chapters exploring how PaC is used with Kubernetes. We investigated several solutions in the context of the PaC selection criteria I introduced in Chapter 1. My goal in the Kubernetes chapters was to present solutions that you can evaluate and from which you can choose the best fit for your needs. Each solution has pros and cons, and I personally think some solutions are better—more mature and functional—than others. However, the decision is yours, and I have given you a starting point from which to make those decisions.
In this chapter, we start to look past Kubernetes to other PaC use cases, and we will begin with how PaC improves infrastructure as code (IaC) practices. This chapter will primarily focus on IaC in AWS.
Before we completely abandon Kubernetes, I want to make sure that you remember the most important part of Kubernetes PaC solutions: the API server request flow.
The Kubernetes API server request flow—introduced in Chapter 4 and illustrated in Figure 11-1—is the most powerful aspect of Kubernetes PaC solutions, as it provides a native means by which preventive controls are applied to Kubernetes clusters.
Figure 11-1. Kubernetes API server request flow
With its mutating and validating webhooks integrated to PaC solutions, the Kubernetes API server request flow applies the well-known patterns of ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access