Scale by Component
Scale pod settings
Use these settings to set the resource values of a pod:
Value | Description | Example |
---|---|---|
cpu | Amount of CPU to use for the pod/container | cpu: 2 cpu: 2.5 |
memory | Amount of RAM to use for the pod/container | memory: 500Gi |
storage | Amount of ephemeral storage to be used: note this type of storage isn't stateful | storage: 10Gi |
data_storage | To scale the PVC for pods that support it, use the data_storage key | data_storage: 1TB |
When specified, both request and limit are set for the specified resource (memory, CPU, storage, data_storage). Use overcommit
or limit_cpu
tunables for more flexibility. See Overcommit for more information.
Configure single pods
Modify single pod settings in the hydrolixcluster.yaml
file.
For example, this setting modifies the intake-head
pods to have two CPUs and 10GiB of RAM allocated:
scale:
intake-head:
cpu: 2
memory: 10Gi
Configure multi-container pods
Some Hydrolix services run as pods with multiple containers. For example, the stream peer service contains both the intake-head
and turbine
containers. The turbine
container is the indexer component that executes transforms and indexes content.
Settings applied to the default intake-head
service don't apply to the turbine
container.
Use the <component>-indexer
name to specify the turbine
component in your hydrolixcluster.yaml
file. For example, for intake
, use intake-indexer
.
See Scale Profiles for a list of pods.
Updated 1 day ago