C. States only Kubernetes which makes it wrong.
A vSphere Namespace sets the resource boundaries where vSphere Pods, VMs, and TKG clusters can run. As a vSphere administrator, you create and configure vSphere Namespaces through the vSphere Client.
When initially created, a vSphere Namespace has unlimited resources within the Supervisor. As a vSphere administrator, you can set limits for CPU, memory, storage, as well as the number of Kubernetes objects that can run within the vSphere Namespace. Storage limitations are represented as storage quotas in Kubernetes. A resource pool is created in vSphere per each vSphere Namespace on the Supervisor
In a Supervisor activated on vSphere Zones, a namespace resource pool is created on each vSphere cluster that is mapped to a zone.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
JMorrison
1 week agoChunky123
1 month, 2 weeks agoyorchiluis
1 month, 4 weeks agosafodz
2 months, 2 weeks ago