Summary
This chapter continued covering the foundational concepts we introduced in Chapter 9, Technical Overview, Management, and Administration, in terms of what it means to operate Cloud Pak for Data in a multi-tenanted fashion, with security and reliability in mind.
We elaborated on the key tenancy requirements, and then focused on the namespace per tenant approach as the best practice for supporting multiple Cloud Pak for Data tenants within the same shared OpenShift Kubernetes cluster. We also described how this recommended approach, along with important organizational structures, helps achieve the key tenancy requirements, starting with how Kubernetes namespaces and OpenShift projects, as a concept, help with enforcing tenant isolations. This chapter also reinforced the importance of the Operator pattern to help in improving the security posture and the different capabilities in the control plane that support tenancy, along with assurances of security and meeting performance...
