How are quotas and permissions guaranteed by vSphere with Tanzu for Tanzu Kubernetes (TKG) clusters that are deployed within a namespace?
How are quotas and permissions guaranteed by vSphere with Tanzu for Tanzu Kubernetes (TKG) clusters that are deployed within a namespace?
Quotas and permissions for Tanzu Kubernetes (TKG) clusters within a namespace are guaranteed by routing quota and permission API calls to vCenter Server via the Supervisor Cluster. The Supervisor Cluster in VMware's vSphere with Tanzu plays a central role in managing and enforcing policies, including quotas and permissions, by acting as an intermediary that handles administrative tasks and ensures that the TKG clusters adhere to the defined policies.
Definitely B.
A is correct
I'm not sure about this one. I'll go with "B" because it seems reasonable. A. By routing quota and permission API calls to vCenter Server via the Supervisor Cluster I'm not sure... why does this have to be API calls? The whole point of Tanzu is that you can do a lot of administration through vCenter and kubectl. B. By ensuring each TKG cluster has a quotas and permissions system built into it natively which enforces all requests This is true, and I guess the best answer. TKG clusters and namespaces leverage inbuilt quota and permissions systems, and these do enforce all requests. C. By having the Supervisor Cluster poll the TKG cluster periodically to ensure adherence to quotas and permissions No... polling is not the way this is done (and a terrible idea because you can do what you want between polls? Ha...) D. By deploying an external authentication solution No, this is certainly handled by TKG, no need for an external one. While "A" looks compelling, "B" seems a better answer. I choose that.