added kb for recommendation on deployment of additional workloads on … - #45
Open
devenkulkarni wants to merge 3 commits into
Open
added kb for recommendation on deployment of additional workloads on …#45devenkulkarni wants to merge 3 commits into
devenkulkarni wants to merge 3 commits into
Conversation
…harvester host cluster
✅ Deploy Preview for harvester-home-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Contributor
|
Maybe we can also consider linking the official statement and document. |
Author
|
Are any changes requested from my end to the KB? |
Author
|
@bk201 Have added the requested changes. Please review and let me know if any further changes are required. |
dnoland1
reviewed
Oct 16, 2023
dnoland1
reviewed
Oct 16, 2023
devenkulkarni
force-pushed
the
kb-deploy-additional-workload
branch
from
October 17, 2023 04:15
d9ddf21 to
41cff07
Compare
LucasSaintarbor
left a comment
LucasSaintarbor
left a comment
Collaborator
There was a problem hiding this comment.
@bk201 Made some wording and formatting changes. Lmk if these changes are okay. Thanks!
Comment on lines
+14
to
+22
| While it is technically possible to deploy additional workloads on the Harvester host cluster, running other workloads or microservices in the same Kubernetes cluster where Harvester is deployed is not officially supported yet. | ||
|
|
||
| Moreover, the deployment of other microservices or workloads may invite the following risks: | ||
| 1. They might not be well integrated and tested on Harvester. Additionally, users need to deploy and troubleshoot them on their own. | ||
| 2. Potential conflict with existing features of Harvester. For instance, high system resource consumption can cause downtime. | ||
| 3. No WebUI support, all operations can only be achieved via kubectl or other CLI tools. | ||
| 4. During system upgrades, they would not be covered. For example, if your workload depends on the Kubernetes version, a Harvester upgrade could require a newer version of Kubernetes, which may break your custom workload. | ||
|
|
||
| Hence, the best practice is to deploy Harvester separately without any additional workloads. Although, we have an experimental feature allowing you to deploy additional workload on Harvester host cluster (bare metal) in Harvester v1.2.0 and for more information on it, please review the [blog](https://www.suse.com/c/rancher_blog/harvester-v1-2-0-release/) and our official documentation [Harvester baremetal container workload support](https://docs.harvesterhci.io/v1.2/rancher/index/#harvester-baremetal-container-workload-support-experimental). |
Collaborator
There was a problem hiding this comment.
Suggested change
| While it is technically possible to deploy additional workloads on the Harvester host cluster, running other workloads or microservices in the same Kubernetes cluster where Harvester is deployed is not officially supported yet. | |
| Moreover, the deployment of other microservices or workloads may invite the following risks: | |
| 1. They might not be well integrated and tested on Harvester. Additionally, users need to deploy and troubleshoot them on their own. | |
| 2. Potential conflict with existing features of Harvester. For instance, high system resource consumption can cause downtime. | |
| 3. No WebUI support, all operations can only be achieved via kubectl or other CLI tools. | |
| 4. During system upgrades, they would not be covered. For example, if your workload depends on the Kubernetes version, a Harvester upgrade could require a newer version of Kubernetes, which may break your custom workload. | |
| Hence, the best practice is to deploy Harvester separately without any additional workloads. Although, we have an experimental feature allowing you to deploy additional workload on Harvester host cluster (bare metal) in Harvester v1.2.0 and for more information on it, please review the [blog](https://www.suse.com/c/rancher_blog/harvester-v1-2-0-release/) and our official documentation [Harvester baremetal container workload support](https://docs.harvesterhci.io/v1.2/rancher/index/#harvester-baremetal-container-workload-support-experimental). | |
| While it is technically possible to deploy additional workloads on a Harvester host cluster, running other workloads or microservices in the same Kubernetes cluster where you deploy Harvester is not officially supported. | |
| Moreover, the deployment of other microservices or workloads may invite the following risks: | |
| - Your workloads might not be well integrated and tested on Harvester, and you would need to deploy and troubleshoot them on your own. | |
| - Potential conflict with existing features of Harvester. For instance, high system resource consumption can cause downtime. | |
| - No Harvester WebUI support. You can only perform all of the operations via kubectl or other CLI tools. | |
| - During system upgrades, covering your workload may not be possible. For example, if your workload depends on a specific version of Kubernetes, a Harvester upgrade could require a newer version of Kubernetes, which may break your custom workload. | |
| The best practice is to deploy Harvester separately without any additional workloads. However, Harvester v1.2.0 introduces an experimental feature allowing you to deploy additional workloads on a Harvester host cluster (bare metal). For more information, please review the [Announcing the Harvester v1.2.0 Release](https://www.suse.com/c/rancher_blog/harvester-v1-2-0-release/#:~:text=BareMetal%20Cloud%20Native%20Workload%20Support%20(Experimental)) blog and our official documentation [Harvester baremetal container workload support (experimental)](https://docs.harvesterhci.io/v1.2/rancher/index/#harvester-baremetal-container-workload-support-experimental). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.