Scalable deployments
Scalable deployments are something we hear about quite often; it might even be considered a buzzword. But it is especially very important with Kubernetes. Writing infrastructure as code to deploy solutions at scale is something we could classify as a requirement for using Kubernetes. Throughout this book, we have started with small deployments; over the course of a couple of chapters, we went from one customer to eight, and now we are preparing our infrastructure to deploy an infinite amount of customer solutions.
Doing all this the traditional way using the YAML language can become very chaotic. Normally, in YAML, we would write a file for a customer to deploy the frontend as we did in Chapter 11 (https://github.com/PacktPublishing/Azure-Containers-Explained/blob/main/CH11/frontend.yaml).
If we inspect this file, we can see some hardcoded values that ideally we would parameterize. Let’s look at the following example for an Ingress resource:
apiVersion...
