From a38731b256bf8205e8d440ec9cdc32f5c039a994 Mon Sep 17 00:00:00 2001 From: jigisha620 Date: Mon, 1 Jul 2024 18:25:13 -0700 Subject: [PATCH] docs: Update docs to indicate requirements limit on NodePool is 100 --- website/content/en/docs/concepts/nodepools.md | 4 ++++ website/content/en/docs/concepts/scheduling.md | 3 +++ website/content/en/preview/concepts/nodepools.md | 4 ++++ website/content/en/preview/concepts/scheduling.md | 4 ++++ website/content/en/v0.32/concepts/nodepools.md | 4 ++++ website/content/en/v0.32/concepts/scheduling.md | 3 +++ website/content/en/v0.35/concepts/nodepools.md | 4 ++++ website/content/en/v0.35/concepts/scheduling.md | 3 +++ website/content/en/v0.36/concepts/nodepools.md | 4 ++++ website/content/en/v0.36/concepts/scheduling.md | 4 ++++ website/content/en/v0.37/concepts/nodepools.md | 4 ++++ website/content/en/v0.37/concepts/scheduling.md | 3 +++ 12 files changed, 44 insertions(+) diff --git a/website/content/en/docs/concepts/nodepools.md b/website/content/en/docs/concepts/nodepools.md index 9a9b9a06d57a..b61602783748 100644 --- a/website/content/en/docs/concepts/nodepools.md +++ b/website/content/en/docs/concepts/nodepools.md @@ -233,6 +233,10 @@ Karpenter prioritizes Spot offerings if the NodePool allows Spot and on-demand i Karpenter also allows `karpenter.sh/capacity-type` to be used as a topology key for enforcing topology-spread. +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} + ### Min Values Along with the combination of [key,operator,values] in the requirements, Karpenter also supports `minValues` in the NodePool requirements block, allowing the scheduler to be aware of user-specified flexibility minimums while scheduling pods to a cluster. If Karpenter cannot meet this minimum flexibility for each key when scheduling a pod, it will fail the scheduling loop for that NodePool, either falling back to another NodePool which meets the pod requirements or failing scheduling the pod altogether. diff --git a/website/content/en/docs/concepts/scheduling.md b/website/content/en/docs/concepts/scheduling.md index 007638e64f3e..437a6f1cda5f 100755 --- a/website/content/en/docs/concepts/scheduling.md +++ b/website/content/en/docs/concepts/scheduling.md @@ -174,6 +174,9 @@ requirements: - key: user.defined.label/type operator: Exists ``` +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} #### Node selectors diff --git a/website/content/en/preview/concepts/nodepools.md b/website/content/en/preview/concepts/nodepools.md index 7385b268e316..0885ee79d82e 100644 --- a/website/content/en/preview/concepts/nodepools.md +++ b/website/content/en/preview/concepts/nodepools.md @@ -233,6 +233,10 @@ Karpenter prioritizes Spot offerings if the NodePool allows Spot and on-demand i Karpenter also allows `karpenter.sh/capacity-type` to be used as a topology key for enforcing topology-spread. +{{% alert title="Note" color="primary" %}} +There is currently a limit of 100 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 100 requirements and labels combined set on your NodePool. +{{% /alert %}} + ### Min Values Along with the combination of [key,operator,values] in the requirements, Karpenter also supports `minValues` in the NodePool requirements block, allowing the scheduler to be aware of user-specified flexibility minimums while scheduling pods to a cluster. If Karpenter cannot meet this minimum flexibility for each key when scheduling a pod, it will fail the scheduling loop for that NodePool, either falling back to another NodePool which meets the pod requirements or failing scheduling the pod altogether. diff --git a/website/content/en/preview/concepts/scheduling.md b/website/content/en/preview/concepts/scheduling.md index 691cb95c0b41..35a9c2d3f773 100755 --- a/website/content/en/preview/concepts/scheduling.md +++ b/website/content/en/preview/concepts/scheduling.md @@ -175,6 +175,10 @@ requirements: operator: Exists ``` +{{% alert title="Note" color="primary" %}} +There is currently a limit of 100 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 100 requirements and labels combined set on your NodePool. +{{% /alert %}} + #### Node selectors Here is an example of a `nodeSelector` for selecting nodes: diff --git a/website/content/en/v0.32/concepts/nodepools.md b/website/content/en/v0.32/concepts/nodepools.md index 7a369b13f326..223f53b828a3 100644 --- a/website/content/en/v0.32/concepts/nodepools.md +++ b/website/content/en/v0.32/concepts/nodepools.md @@ -243,6 +243,10 @@ spec: {{% /alert %}} +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} + ## spec.template.spec.nodeClassRef This field points to the Cloud Provider NodeClass resource. Learn more about [EC2NodeClasses]({{}}). diff --git a/website/content/en/v0.32/concepts/scheduling.md b/website/content/en/v0.32/concepts/scheduling.md index 48d49d9f0a52..147f4e00896e 100755 --- a/website/content/en/v0.32/concepts/scheduling.md +++ b/website/content/en/v0.32/concepts/scheduling.md @@ -171,6 +171,9 @@ requirements: - key: user.defined.label/type operator: Exists ``` +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} #### Node selectors diff --git a/website/content/en/v0.35/concepts/nodepools.md b/website/content/en/v0.35/concepts/nodepools.md index 9a9b9a06d57a..b61602783748 100644 --- a/website/content/en/v0.35/concepts/nodepools.md +++ b/website/content/en/v0.35/concepts/nodepools.md @@ -233,6 +233,10 @@ Karpenter prioritizes Spot offerings if the NodePool allows Spot and on-demand i Karpenter also allows `karpenter.sh/capacity-type` to be used as a topology key for enforcing topology-spread. +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} + ### Min Values Along with the combination of [key,operator,values] in the requirements, Karpenter also supports `minValues` in the NodePool requirements block, allowing the scheduler to be aware of user-specified flexibility minimums while scheduling pods to a cluster. If Karpenter cannot meet this minimum flexibility for each key when scheduling a pod, it will fail the scheduling loop for that NodePool, either falling back to another NodePool which meets the pod requirements or failing scheduling the pod altogether. diff --git a/website/content/en/v0.35/concepts/scheduling.md b/website/content/en/v0.35/concepts/scheduling.md index 76b5e362c10d..0674870f5b07 100755 --- a/website/content/en/v0.35/concepts/scheduling.md +++ b/website/content/en/v0.35/concepts/scheduling.md @@ -172,6 +172,9 @@ requirements: - key: user.defined.label/type operator: Exists ``` +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} #### Node selectors diff --git a/website/content/en/v0.36/concepts/nodepools.md b/website/content/en/v0.36/concepts/nodepools.md index 9a9b9a06d57a..b61602783748 100644 --- a/website/content/en/v0.36/concepts/nodepools.md +++ b/website/content/en/v0.36/concepts/nodepools.md @@ -233,6 +233,10 @@ Karpenter prioritizes Spot offerings if the NodePool allows Spot and on-demand i Karpenter also allows `karpenter.sh/capacity-type` to be used as a topology key for enforcing topology-spread. +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} + ### Min Values Along with the combination of [key,operator,values] in the requirements, Karpenter also supports `minValues` in the NodePool requirements block, allowing the scheduler to be aware of user-specified flexibility minimums while scheduling pods to a cluster. If Karpenter cannot meet this minimum flexibility for each key when scheduling a pod, it will fail the scheduling loop for that NodePool, either falling back to another NodePool which meets the pod requirements or failing scheduling the pod altogether. diff --git a/website/content/en/v0.36/concepts/scheduling.md b/website/content/en/v0.36/concepts/scheduling.md index 6d94aeb17272..c942ab3b3ef7 100755 --- a/website/content/en/v0.36/concepts/scheduling.md +++ b/website/content/en/v0.36/concepts/scheduling.md @@ -174,6 +174,10 @@ requirements: operator: Exists ``` +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} + #### Node selectors Here is an example of a `nodeSelector` for selecting nodes: diff --git a/website/content/en/v0.37/concepts/nodepools.md b/website/content/en/v0.37/concepts/nodepools.md index 9a9b9a06d57a..b61602783748 100644 --- a/website/content/en/v0.37/concepts/nodepools.md +++ b/website/content/en/v0.37/concepts/nodepools.md @@ -233,6 +233,10 @@ Karpenter prioritizes Spot offerings if the NodePool allows Spot and on-demand i Karpenter also allows `karpenter.sh/capacity-type` to be used as a topology key for enforcing topology-spread. +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} + ### Min Values Along with the combination of [key,operator,values] in the requirements, Karpenter also supports `minValues` in the NodePool requirements block, allowing the scheduler to be aware of user-specified flexibility minimums while scheduling pods to a cluster. If Karpenter cannot meet this minimum flexibility for each key when scheduling a pod, it will fail the scheduling loop for that NodePool, either falling back to another NodePool which meets the pod requirements or failing scheduling the pod altogether. diff --git a/website/content/en/v0.37/concepts/scheduling.md b/website/content/en/v0.37/concepts/scheduling.md index 007638e64f3e..437a6f1cda5f 100755 --- a/website/content/en/v0.37/concepts/scheduling.md +++ b/website/content/en/v0.37/concepts/scheduling.md @@ -174,6 +174,9 @@ requirements: - key: user.defined.label/type operator: Exists ``` +{{% alert title="Note" color="primary" %}} +There is currently a limit of 30 on the total number of requirements on both the NodePool and the NodeClaim. It's important to note that `spec.template.metadata.labels` are also propagated as requirements on the NodeClaim when it's created, meaning that you can't have more than 30 requirements and labels combined set on your NodePool. +{{% /alert %}} #### Node selectors