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.

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

fix on consolidation #213

Merged
merged 1 commit into from
Sep 8, 2022
Merged
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions content/karpenter/050_karpenter/consolidation.md
Original file line number Diff line number Diff line change
Expand Up @@ -267,6 +267,14 @@ There are other cases that Karpenter will consider when consolidating. Consolida
Finally, Karpenter consolidation will not attempt to consolidate a node that is running pods that are not owned by a controller (e.g. a ReplicaSet). In general we cannot assume that these pods would be recreated if they were evicted from the node that they are currently running on.
{{% /expand %}}

#### 7) Scale the replicas to 0.

In preparation for the next section, scale replicas to 0 using the following command.

```
kubectl scale deployment inflate --replicas 0
```


## What Have we learned in this section:

Expand Down