More often than not, a pod contains only one container. And this approach is correct for countless cases, although it is not the only approach we can adopt when we bring our Cloud Native application to a Kubernetes cluster. However, having multiple containers in the same pod brings benefits only in certain cases, mapped by Design Patterns suitably designed to ensure the simplicity of application containers, adding capabilities to solve specific problems using other containers. We will see together the most common patterns in detail, trying to understand in which occasion they are most useful.