Cluster Orchestrator 1/3: Overview and Getting Started #10556
Conversation
joeyouss
requested review from
josephdlopez,
karanshetty53,
rajarshee-harness and
jyotiarora-harness
as code owners
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6847ff1746db84cc6e7816f9--harness-developer.netlify.app |
| ::: | ||
|
|
||
| Harness’ Cloud Cost Management is centered on three key pillars: Cost Visibility, Cost Optimization and Cost Governance. | ||
| Currently AutoStopping, Recommendations and Commitment Orchestrator (in beta) are present under cost optimisation. Harness CCM has added Cluster Orchestrator for EKS (Beta) to enhance workload-driven autoscaling and intelligent management of AWS Spot instances, contributing to overall cost efficiency. |
There was a problem hiding this comment.
Do not think commitment orch is in beta anymore
|
|
||
| ## Cluster Infrastructure and challenges | ||
|
|
||
| <DocImage path={require('./static/challenges.png')} width="50%" height="50%" title="Click to view full size image" /> |
There was a problem hiding this comment.
nit: Can we have a newer version of this image and also include the problems solved by cluster orch such as bin packing and workload distribution?
|
|
||
| <DocImage path={require('./static/challenges.png')} width="50%" height="50%" title="Click to view full size image" /> | ||
|
|
||
| #### 1. Dynamic Workload Balancing ✓ SOLVED |
There was a problem hiding this comment.
We need to revisit and reword these items. @karanshetty53
|
|
||
| ## Harness Cluster Orchestrator for Amazon Elastic Kubernetes Service (EKS) | ||
|
|
||
| The **Harness Cluster Orchestrator** for Amazon Elastic Kubernetes Service (EKS), a component of the Harness Cloud Cost Management (CCM) module, is designed to tackle the obstacles listed above. It **intelligently scales EKS cluster nodes** according to actual workload requirements. Additionally, by leveraging CCM's **distributed Spot orchestration capability**, you can **save up to 90% on cloud costs** with Amazon EC2 Spot Instances. |
There was a problem hiding this comment.
We need a table here for feature comparison
| ## Prerequisites | ||
|
|
||
| - [AWS EKS cluster with Metrics Server installed](https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html) | ||
| - [Harness Kubernetes connector](/docs/platform/connectors/cloud-providers/add-a-kubernetes-cluster-connector) |
There was a problem hiding this comment.
Only one pre requisite, ie the CCM K8s connector
| ## Quick Start | ||
|
|
||
| 1. Log in to [Harness](https://app.harness.io) and go to **Cloud Costs** → **Cluster Orchestrator** | ||
| 2. Click on "Add New Cluster" |
There was a problem hiding this comment.
I guess Steps 2 and 3 can be removed from here. We can start from a state where the customer already has the kubernetes connector created. We can just start from clicking enable button
| - [Advanced](/docs/cloud-cost-management/get-started/onboarding-guide/set-up-cost-visibility-for-kubernetes) | ||
| 4. After this, your created connector will show up on the home page of Cluster Orchestrator. | ||
| 5. Choose an enablement method and follow the steps listed on the respective pages: | ||
| - **kubectl**: [Details](/docs/cloud-cost-management/use-ccm-cost-optimization/cluster-orchestrator/setting-up-co#installation-via-kubectl) |
There was a problem hiding this comment.
can be, onboard with a single command
| 4. After this, your created connector will show up on the home page of Cluster Orchestrator. | ||
| 5. Choose an enablement method and follow the steps listed on the respective pages: | ||
| - **kubectl**: [Details](/docs/cloud-cost-management/use-ccm-cost-optimization/cluster-orchestrator/setting-up-co#installation-via-kubectl) | ||
| - **Helm**: [Details](/docs/cloud-cost-management/use-ccm-cost-optimization/cluster-orchestrator/setting-up-co#helm-based-installation) |
There was a problem hiding this comment.
can be terrafom and helm installation for advanced installation options
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: