-
Notifications
You must be signed in to change notification settings - Fork 95
Add glossary entries for commonly used terms #947
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Jillian <jillian.maroket@suse.com>
Signed-off-by: Jillian <jillian.maroket@suse.com>
|
Signed-off-by: Jillian <jillian.maroket@suse.com>
starbops
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. Please check the comments below.
| Group of integrated Kubernetes worker machines that run in VMs on top of a Harvester cluster. | ||
| Group of integrated Kubernetes worker machines that run in virtual machines on top of a Harvester cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can be wrong about this, but the term Kubernetes "worker" machines sounds like it only applies to the "worker-role" nodes, which is not true. Is there a better term describing it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@starbops Thank you for reviewing. The definitions for guest cluster and guest node were based on details provided by @m-ildefons and @tserong in PR #539 . PTAL at their comments.
| ## **guest node** / **guest cluster node** | ||
|
|
||
| Kubernetes worker VM that uses guest cluster resources to run container workloads. | ||
| Kubernetes worker virtual machine that uses guest cluster resources to run container workloads. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kinda get confused by this statement. I suppose this sentence tries to convey that "those virtual machines, as guest nodes, use/occupy the underlying Harvester cluster resources to run container workloads on the guest cluster".
|
|
||
| ## **Harvester Cloud Provider** | ||
|
|
||
| Component that enables a Rancher-managed Harvester cluster to function as a [native cloud backend for guest Kubernetes clusters](../rancher/cloud-provider.md). The Harvester Cloud Provider integrates the Kubernetes cloud controller manager (CCM) and container storage interface (CSI) driver, allowing guest clusters to dynamically request and manage Harvester-native resources (load balancer and storage) without manual intervention. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To my knowledge, the Harvester Cloud Provider and the Harvester CSI Driver are two separate components; the latter should be elaborated on in the next section.
|
|
||
| ## **Harvester CSI Driver** | ||
|
|
||
| Driver that provides a standard container storage interface (CSI) for guest Kubernetes clusters running on top of Harvester virtual machines. This component [connects guest clusters to the underlying Harvester cluster](../rancher/csi-driver.md) and enables hotplugging of volumes to the virtual machines to provide native storage performance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The paragraph itself is correct. However, I would also suggest emphasizing the container viewpoint, as that is what users care about more.
The Harvester CSI Driver enables container workloads running on guest clusters to use volumes backed by the underlying Harvester cluster storage, thereby providing much better performance.
|
@ihcsim Please review the term definitions. Thank you. |
The Localization team is planning to translate the SUSE Virtualization doc, so I was asked to provide definitions for an initial set of terms. Due to task scheduling constraints, I decided to split the terms into two sets.
Set 1 (covered in this PR):
Set 2: