kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #13178 from olemarkus/karpenter-max-pods 

Karpenter on kOps will now use approperiate max pods
This commit is contained in:
Kubernetes Prow Robot 2022-02-15 01:20:03 -08:00 committed by GitHub
parent df493af1a0 6493791a41
commit c9cd710b59
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/operations/karpenter.md
View File

@ -55,10 +55,6 @@ If you do not specify a mixed instances policy, only the instance type specified
kOps will ignore the InstanceGroup `spec.subnets` configuration and unconditionally add all subnets eligible to run Nodes to all Provisioners. It is not currently possible to create Provisioners limited only to certain subnets.
### CNI expectations
Karpenter assumes the CNI is `amazonaws` when it calculates the maximum number of Pods that fit on a node. For other CNIs this means that Karpenter will calculate too few Pods on for smaller instances and too many Pods on larger instances. The default Karpenter-managed InstanceGroup is configured to avoid very large instance types for this reason.
### Karpenter-managed Launch Templates
On EKS, Karpener creates its own launch templates for Provisioners. These launch templates will not work with a kOps cluster for a number of reasons. Most importantly, they do not use supported AMIs and they do not install and configure nodeup, the instance-side kOps component. The Karpenter features that require Karpenter to directly manage launch templates will not be available on kOps.