Difference between revisions of "TopologyKey:"
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
https://karpenter.sh/preview/concepts/scheduling/ | https://karpenter.sh/preview/concepts/scheduling/ | ||
| − | The three supported topologyKey values that Karpenter supports are: | + | The three supported [[topologyKey]] values that Karpenter supports are: |
[[topology.kubernetes.io/zone]] | [[topology.kubernetes.io/zone]] | ||
| Line 14: | Line 14: | ||
[[nodeSelector:]] | [[nodeSelector:]] | ||
| + | [[Kubernetes Pod Topology Spread Constraints]] | ||
| + | == See also == | ||
| + | * {{Karpenter}} | ||
| − | + | [[Category:Karpenter]] | |
Latest revision as of 09:01, 20 January 2023
topologyKey: kubernetes.io/hostname
https://karpenter.sh/preview/concepts/scheduling/ The three supported topologyKey values that Karpenter supports are:
topology.kubernetes.io/zone kubernetes.io/hostname karpenter.sh/capacity-type
nodeSelector: Kubernetes Pod Topology Spread Constraints
See also[edit]
- Karpenter,
karpenter.sh, provisioners.karpenter.sh, Karpenter releases, best practices,karpenter.sh/capacity-type, karpenter.sh/discovery,kind: Provisioner, kind: AWSNodeTemplate,kubectl provisioner,TopologyKey, FailedDraining, Evict, DisruptionBlocked, Karpenter logs,controller., ttlSecondsUntilExpired, KEDA, NodePools, Kind: NodePool, Workload Consolidation, Disruption controls
Advertising:
