Skip to main content
Skip table of contents

Configuring Node Sizes with ExoInstanceTypes

An ExoInstanceType specifies a CPU & Memory size configuration for a x-compute node. Each AWS instance type has a corresponding ExoInstanceType, with the same number of CPU’s and a memory adjusted for overhead. A node with the exoinstancetype family.size is guaranteed to fit on an AWS instance with type family.size.

Example
The exoinstancetype m5.2xlarge has 8 CPU’s and (32 - Overhead) GiB of memory. Any x-compute node with the size m5.2xlarge is guaranteed to be able to fit on a AWS instance of type m5.2xlarge.

Usage

You can adjust what ExoInstanceTypes are allowed by configuring the requirements of your ExoNodePool. There are four requirement keys that can configure available ExoInstanceTypes. These keys support the In and NotIn operators.

Key Name

Description

Example Values

karpenter.k8s.exostellar/instance-category

Allows ExoInstanceTypes (not) in the specified instance categories.

[“c”, “m”, “r]

karpenter.k8s.exostellar/instance-family

Allows ExoInstanceTypes (not) in the specified instance families.

[“m5”, “m5d”, “c5”, “c5d”, “r5”]

node.kubernetes.io/instance-type

Allows ExoInstanceTypes (not) in the specified instance types.

[“r6i.4xlarge”, “m5.8xlarge”]

karpenter.k8s.aws/instance-cpu

Allows ExoInstanceTypes whose vCPU count is (not) within the specified cpu count list.

[“4”, “8”, “16”, “32”]

It's recommended to match your ExoNodePool’s exoinstancetype requirements with your worker’s allowed instance types, which are set to [m5] by default.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.