From 54d1113fc70fbbf4ca99171fb33b99f284628c98 Mon Sep 17 00:00:00 2001 From: Devendra Kulkarni Date: Tue, 10 Oct 2023 13:52:32 +0530 Subject: [PATCH 1/3] added kb for recommendation on deployment of additional workloads on harvester host cluster --- ...y-additional-workload-on-harvester-host.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 kb/2023-10-10/deploy-additional-workload-on-harvester-host.md diff --git a/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md b/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md new file mode 100644 index 00000000..fd5f622f --- /dev/null +++ b/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md @@ -0,0 +1,22 @@ +--- +title: Additional workload deployment on Harvester Host Cluster +description: Recommendation on deployment of additional workloads on Harvester Cluster +slug: additional_workload_deployment_on_harvester +authors: + - name: Devendra Kulkarni + title: Technical Support Engineer + url: https://github.com/devenkulkarni + image_url: https://github.com/devenkulkarni.png +tags: [harvester, workloads, host, cluster , resources, WebUI] +hide_table_of_contents: false +--- + +While it is technically possible to deploy additional worklaods on the Harvester Host Cluster, running other workloads or microservices in the same Kubernetes cluster where Harvester is deployed on is not recommended. + +Moreover, deployment of other microservices or workloads may invite 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 achived via kubectl or other CLI tools. +(4) During system upgrade, they would not be covered. + +Hence, Best practice is to deploy Harvester seperately without any additional workloads. From 41cff07ae633a0ccf0643b159b7466e85f803d2e Mon Sep 17 00:00:00 2001 From: Devendra Kulkarni Date: Fri, 13 Oct 2023 00:31:12 +0530 Subject: [PATCH 2/3] Modified the kb with requested changes --- .../deploy-additional-workload-on-harvester-host.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md b/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md index fd5f622f..f49fae7c 100644 --- a/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md +++ b/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md @@ -11,12 +11,12 @@ tags: [harvester, workloads, host, cluster , resources, WebUI] hide_table_of_contents: false --- -While it is technically possible to deploy additional worklaods on the Harvester Host Cluster, running other workloads or microservices in the same Kubernetes cluster where Harvester is deployed on is not recommended. +While it is technically possible to deploy additional worklaods on the Harvester Host Cluster, running other workloads or microservices in the same Kubernetes cluster where Harvester is deployed on is not officially supported yet. Moreover, deployment of other microservices or workloads may invite 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 achived via kubectl or other CLI tools. +(3) No WebUI support, all operations can only be achieved via kubectl or other CLI tools. (4) During system upgrade, they would not be covered. -Hence, Best practice is to deploy Harvester seperately without any additional workloads. +Hence, best practice is to deploy Harvester seperately 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). From d58140653e9e9a38baf73d02a54a9192ef86e152 Mon Sep 17 00:00:00 2001 From: Devendra Kulkarni Date: Tue, 17 Oct 2023 11:34:02 +0530 Subject: [PATCH 3/3] Spell checks and suggested changes revised --- ...y-additional-workload-on-harvester-host.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md b/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md index f49fae7c..4b061b86 100644 --- a/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md +++ b/kb/2023-10-10/deploy-additional-workload-on-harvester-host.md @@ -1,22 +1,22 @@ --- -title: Additional workload deployment on Harvester Host Cluster -description: Recommendation on deployment of additional workloads on Harvester Cluster +title: Additional workload deployment on Harvester host cluster +description: Recommendation on the deployment of additional workloads on the Harvester cluster slug: additional_workload_deployment_on_harvester authors: - name: Devendra Kulkarni title: Technical Support Engineer url: https://github.com/devenkulkarni image_url: https://github.com/devenkulkarni.png -tags: [harvester, workloads, host, cluster , resources, WebUI] +tags: [harvester, workloads, host, cluster, resources, WebUI] hide_table_of_contents: false --- -While it is technically possible to deploy additional worklaods on the Harvester Host Cluster, running other workloads or microservices in the same Kubernetes cluster where Harvester is deployed on is not officially supported yet. +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, deployment of other microservices or workloads may invite 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 upgrade, they would not be covered. +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, best practice is to deploy Harvester seperately 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). +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).