Skip to content
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.

Sign up for GitHub

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

Update consolidation.md #236

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+3 −3
Open

Update consolidation.md #236

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f258100
Update consolidation.md
oak2278 Feb 10, 2023
acd7ca2
Update consolidation.md
oak2278 Feb 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/karpenter/050_karpenter/consolidation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ In the previous section we did set the default provisioner configured with a spe
Automated deprovisioning is configured through the ProvisionerSpec `.ttlSecondsAfterEmpty`, `.ttlSecondsUntilExpired` and `.consolidation.enabled` fields. If these are not configured, Karpenter will not default values for them and will not terminate nodes.
{{% /notice %}}

There is another way to configure Karpenter to deprovision nodes called **Consolidation**. This mode is preferred for workloads such as microservices and is imcompatible with setting up the `ttlSecondsAfterEmpty` . When set in consolidation mode Karpenter works to actively reduce cluster cost by identifying when nodes can be removed as their workloads will run on other nodes in the cluster and when nodes can be replaced with cheaper variants due to a change in the workloads.
There is another way to configure Karpenter to deprovision nodes called **Consolidation**. This mode is preferred for workloads such as microservices and is incompatible with setting up the `ttlSecondsAfterEmpty` . When set in consolidation mode Karpenter works to actively reduce cluster cost by identifying when nodes can be removed as their workloads will run on other nodes in the cluster and when nodes can be replaced with cheaper variants due to a change in the workloads.

Before we proceed to see how Consolidation works, let's change the default provisioner configuration:
```
Expand Down Expand Up @@ -59,7 +59,7 @@ EOF
## Challenge

{{% notice tip %}}
You can use **Kube-ops-view** or just plain **kubectl** cli to visualize the changes and answer the questions below. In the answers we will provide the CLI commands that will help you check the resposnes. Remember: to get the url of **kube-ops-view** you can run the following command `kubectl get svc kube-ops-view | tail -n 1 | awk '{ print "Kube-ops-view URL = http://"$4 }'`.
You can use **Kube-ops-view** or just plain **kubectl** cli to visualize the changes and answer the questions below. In the answers we will provide the CLI commands that will help you check the responses. Remember: to get the url of **kube-ops-view** you can run the following command `kubectl get svc kube-ops-view | tail -n 1 | awk '{ print "Kube-ops-view URL = http://"$4 }'`.
Note the current version of Kube-ops-view sometimes takes time to reflect the correct state of the cluster.
{{% /notice %}}

Expand Down Expand Up @@ -288,4 +288,4 @@ In this section we have learned:

* **Delete** Consolidation does also include events where instances are moved from `on-demand` to `spot`, however karpenter does not trigger **Replace** to make Spot node smaller as this can have an impact on the level of interruptions.

* Karpenter uses cordon and drain [best practices](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) to terminate nodes. to make it safer, Karpenter adds a finalizer so that a `kubernetes delete node` command, results in a graceful termination that remove the node safely from the cluster.
* Karpenter uses cordon and drain [best practices](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) to terminate nodes. to make it safer, Karpenter adds a finalizer so that a `kubernetes delete node` command, results in a graceful termination that remove the node safely from the cluster.