You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Cloud providers typically do not expose the Control Plane nodes to their customers in their Managed Kubernetes solutions. The customer will typically only see the Worker nodes in their cluster.
This enhances security and also reduces the risk that the tenant can negatively impact the health of the Kubernetes cluster which is very important for Cloud Providers offering uptime SLA for CAPVCD clusters.
Describe the solution you'd like
Have an option of deploying the control plane nodes in a different OrgVDC where the tenant does not have any access, and do not register the control plane nodes with the API server.
In this scenario, when the customer runs kubectl get nodes, they only see the worker nodes. And when they log in to the Cloud Director UI, they only see the VMs relating to the worker nodes.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Cloud providers typically do not expose the Control Plane nodes to their customers in their Managed Kubernetes solutions. The customer will typically only see the Worker nodes in their cluster.
This enhances security and also reduces the risk that the tenant can negatively impact the health of the Kubernetes cluster which is very important for Cloud Providers offering uptime SLA for CAPVCD clusters.
Describe the solution you'd like
Have an option of deploying the control plane nodes in a different OrgVDC where the tenant does not have any access, and do not register the control plane nodes with the API server.
In this scenario, when the customer runs kubectl get nodes, they only see the worker nodes. And when they log in to the Cloud Director UI, they only see the VMs relating to the worker nodes.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: