Removed constraints+overrides verbiage in favor of layered constraints

aws · Feb 10, 2022 · 4834a37 · 4834a37
1 parent 5ddf71b
commit 4834a37
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/README.md b/README.md
@@ -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/)!