GLYPH<SM590000> Use a Kubernetes  imagePullSecret  to store image registry credentials. Similarly, because  personal information must be safeguarded, the  imagePullSecret  feature that is on  Kubernetes also allows for safely storing and retrieving registry credentials in such a way  that only authorized personnel with access to the secret can manipulate the registry. In general, do not store personal information in container images or registry namespaces. For  proper protection and encryption, store registry credentials in Kubernetes  imagePullSecrets and other personal information in Kubernetes secrets. Because images are composed of  several layers, as described in “Images and containers” on page 202, deleting an image might  not be sufficient to completely remove this personal information if personal information is  stored in a previous layer of an image. This section provides an introduction to how IBM LinuxONE can meet the scalability and  performance demands when orchestrating containers by using Kubernetes. It also introduces  different deployment strategies that are commonly used for microservices and containers.  The union of containers and Kubernetes-based technologies represents a huge shift on the  way that cloud-ready and traditional applications can be modernized, scaled, and deployed to  satisfy the fast changing requirements that were introduced by the present digital era. With  the growing adoption of on-premises environments and containers, the requirements for a  reliable and agile infrastructure are, once again, going to be the determinant factor for the  success of an organization. One of the common problems that typically occur during the deployment of a container-based  infrastructure lies on hardware and architectural limits. The choice of the right architecture is  important because several requirements are imposed during the container orchestration  process.  Also, organizations want to simplify operations, meet compliance requirements, ensure  overall system-wide security, and reduce costs. In that sense, the IBM LinuxONE platform is  the ideal choice for running Kubernetes, containers, and traditional Linux-based workloads in  a single hardware footprint. A common scenario that is seen in Kubernetes implementations in on-premises  infrastructures goes back to a classic problem that is commonly seen during the  pre-virtualization era: server farming$^{2}$. This issue occurs because although containers are  typically lightweight components, great processing power is required to orchestrate, scale,  and manage an enterprise infrastructure. In that sense, it is important to consider an  organization’s needs and plan for future growth. Implementing a container-based infrastructure comes with its own challenges. Moreover, the  effects of server farms can be disastrous for a Kubernetes cluster and its applications. Server  farming can cause the following adverse effects: GLYPH<SM590000> Higher complexity: The overall infrastructure is much more complex to build and manage  because several servers are spread across the data center 2 In this context,  server farms  refers to an increased management complexity that was introduced by having several  distributed systems spread across an infrastructure because their capacity alone cannot meet the required  demand. Chapter 7. Securing IBM Cloud Private and Microservices on LinuxONE  213 7.4.1 IBM LinuxONE as the container platform 7.4 Containers management at scale