The Getting Started with Karpenter guide uses CloudFormation to bootstrap the cluster to enable Karpenter to create and manage nodes, as well as to allow Karpenter to respond to interruption events. This document describes the cloudformation.yaml file used in that guide. These descriptions should allow you to understand: What Karpenter is authorized to do with your EKS cluster and AWS resources when using the cloudformation.yaml file What permissions you need to set up if you are adding Karpe...| Karpenter – Reference
Karpenter makes several metrics available in Prometheus format to allow monitoring cluster provisioning status. These metrics are available by default at karpenter.kube-system.svc.cluster.local:8080/metrics configurable via the METRICS_PORT environment variable documented here karpenter_ignored_pod_count Number of pods ignored during scheduling by Karpenter Stability Level: ALPHA karpenter_build_info A metric with a constant ‘1’ value labeled by version from which karpenter was built. Sta...| Karpenter – Reference
Karpenter observes Kubernetes pods and launches nodes in response to those pods’ scheduling constraints. Karpenter does not perform the actual scheduling and instead waits for kube-scheduler to schedule the pods. When running in AWS, Karpenter is typically installed onto EC2 instances that run in EKS Clusters. Karpenter relies on public facing AWS APIs and standard IAM Permissions. Karpenter uses AWS-SDK-Go v1, and AWS advises that credentials are provided using IAM Roles for Service Accounts.| karpenter.sh
Evaluate Instance Type Resources| karpenter.sh