Skip to main content

Default Node Types

IOMETE ships defaults tailored to each cloud provider, imported on first startup. You can edit or delete any of them at any time. See Node Types Overview for background and Node Type Sizing for guidance on choosing the right size.

On-Premises

On-premises defaults use fixed CPU and memory values with no cloud-provider overhead applied.

NameComponentCPUMemoryDescription
driver-smallDriver1 vCPU8 GiBSmall driver
driver-mediumDriver2 vCPU16 GiBMedium driver
driver-largeDriver4 vCPU32 GiBLarge driver
driver-x-largeDriver8 vCPU64 GiBExtra-large driver
exec-smallExecutor2 vCPU16 GiBSmall executor
exec-mediumExecutor4 vCPU32 GiBMedium executor
exec-largeExecutor8 vCPU64 GiBLarge executor
exec-x-largeExecutor16 vCPU128 GiBExtra-large executor

AWS

AWS defaults reflect allocatable CPU and memory after Kubernetes system overhead, so the numbers aren't round. Executor node types include spot-instance support.

NameComponentCPUMemorySpotDescription
driver-smallDriver~1 vCPU~6 GiBNosmall (1vCPU/8GiB)
driver-mediumDriver~2 vCPU~14 GiBNomedium (2vCPU/16GiB)
driver-largeDriver~4 vCPU~29 GiBNolarge (4vCPU/32GiB)
driver-x-largeDriver~8 vCPU~61 GiBNox-large (8vCPU/64GiB)
exec-smallExecutor~2 vCPU~14 GiBYessmall (2vCPU/16GiB/118GB SSD)
exec-mediumExecutor~4 vCPU~29 GiBYesmedium (4vCPU/32GiB/237GB SSD)
exec-largeExecutor~8 vCPU~61 GiBYeslarge (8vCPU/64GiB/474GB SSD)
exec-x-largeExecutor~16 vCPU~123 GiBYesx-large (16vCPU/128GiB/950GB NVMe)

GCP

GCP defaults map to specific machine types. Values reflect allocatable resources after Kubernetes overhead, which on GKE is substantial: each tier therefore sits on a larger machine than the equivalent tier on other providers.

NameComponentCPUMemoryDescription
driver-smallDriver~2 vCPU~9 GiBe2-highmem-2 (2vCPU/16GiB)
driver-mediumDriver~4 vCPU~24 GiBe2-highmem-4 (4vCPU/32GiB)
driver-largeDriver~8 vCPU~54 GiBe2-highmem-8 (8vCPU/64GiB)
driver-x-largeDriver~16 vCPU~115 GiBe2-highmem-16 (16vCPU/128GiB)
exec-smallExecutor~2 vCPU~9 GiBc2d-highmem-2 (2vCPU/16GiB/375GB SSD)
exec-mediumExecutor~4 vCPU~24 GiBc2d-highmem-4 (4vCPU/32GiB/375GB SSD)
exec-largeExecutor~8 vCPU~54 GiBc2d-highmem-8 (8vCPU/64GiB/700GB SSD)
exec-x-largeExecutor~16 vCPU~115 GiBc2d-highmem-16 (16vCPU/128GiB/1500GB SSD)

Azure

Azure defaults reflect allocatable CPU and memory after Kubernetes system overhead, so the numbers aren't round.

NameComponentCPUMemoryDescription
driver-smallDriver~2 vCPU~5 GiBsmall (2vCPU/8GiB)
driver-mediumDriver~2 vCPU~12 GiBmedium (2vCPU/16GiB)
driver-largeDriver~4 vCPU~26 GiBlarge (4vCPU/32GiB)
driver-x-largeDriver~8 vCPU~57 GiBx-large (8vCPU/64GiB)
exec-smallExecutor~2 vCPU~12 GiBsmall (2vCPU/16GiB)
exec-mediumExecutor~4 vCPU~26 GiBmedium (4vCPU/32GiB)
exec-largeExecutor~8 vCPU~57 GiBlarge (8vCPU/64GiB)
exec-x-largeExecutor~16 vCPU~116 GiBx-large (16vCPU/128GiB)