Defining Container Memory and CPU Resources

Getting familiar with the terminologies

So far, we have not specified how much memory and CPU containers should be used, nor what their limits should be. If we do that, Kubernetes’ scheduler will have a much better idea about the needs of those containers, and it’ll make much better decisions on which nodes to place the Pods and what to do if they start misbehaving.

Looking into the definition

Let’s take a look at a modified go-demo-2 definition in go-demo-2-random.yml. The specification is almost the same as those we used before. The only new entries are in the resources section.