vpshere Docu - Use consistent Naming and explain usage of cloud users
- Dominant language
- SCSS
- Stars
- 19
- Forks
- 117
- Avg merge
- 13h 29m
- Merged PRs (30d)
- 13
Description
The https://docs.kubermatic.com/kubermatic/master/architecture/requirements/support_policy/provider_support_matrix/vsphere/vsphere/#user-cluster is not optimal:
- Seed Cluster (Naming is misleading) - holding the cloud provider CCM credentials - Lower permissions what are visible inside of user clusters, see #4974
- User Cluster - stored in the seed cluster for the machine controller to create and manage machines for their cluster. This higher privileged user won't get exposed the user clusters.
We should sync the used naming of UI / Docu / permissions
Contributor guide
Research direction
Open the linked vSphere support-policy page and read #4974; compare the Seed Cluster and User Cluster terminology with the UI and permission descriptions shown in the issue. Done means the names and explanations of cloud-user permissions are consistent across those documented surfaces.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100