1 Answer
- Newest
- Most votes
- Most comments
1
I was able to overcome this by specifying kubelet config setting via the YAML configuration passed directly to nodeadm via user-data, for example:
Content-Type: application/node.eks.aws
MIME-Version: 1.0
---
apiVersion: node.eks.aws/v1alpha1
kind: NodeConfig
spec:
cluster:
name: my-cluster
apiServerEndpoint: https://xxxxx.yy.us-east-1.eks.amazonaws.com
certificateAuthority: xyz
cidr: 10.100.0.0/16
kubelet:
config:
maxPods: 110
answered a month ago
Relevant content
- asked 8 months ago
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 14 days ago
- AWS OFFICIALUpdated 2 months ago