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

Removed constraints+overrides verbiage in favor of layered constraints #1316

Merged
merged 1 commit into from
Feb 10, 2022
+1 −1
Merged

Removed constraints+overrides verbiage in favor of layered constraints #1316

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Karpenter works by:

For most use cases, a cluster’s capacity can be managed by a single Karpenter Provisioner.
However, you can define multiple Provisioners, enabling use cases like isolation, entitlements, and sharding.
Using a combination of defaults and overrides, Karpenter determines the availability zone, instance type, capacity type, machine image, and scheduling constraints for pods it manages.
Provisioner requirements are layered with pod requirements to launch a node with the right properties, including taints, labels, availability zone, instance type, operating system, and more.

Come discuss Karpenter in the [#karpenter channel](https://kubernetes.slack.com/archives/C02SFFZSA2K) in the [Kubernetes slack](https://slack.k8s.io/)!

Expand Down