Advanced configuration

Optional configuration behind the defaults the deployment derives. Nothing on this page is needed for a standard install: the values file in the deployment guide is the supported shape, and everything here overrides a default that already works.

Audience: IT (the enabler)

A custom StorageClass for the data root

On AWS (infrastructure.platform: aws in the values file) the deployment creates a default StorageClass for the data root: gp3 on the EBS CSI driver, encrypted with your KMS key, at gp3's baseline performance (3,000 IOPS, 125 MiB/s). Most deployments need nothing else.

If you want a class of your own — provisioned IOPS or throughput above the baseline, volume tags, or a class your organization already operates — create one that meets the contract in Storage for the data root and name it in the values file, which suppresses the created default:

vfs:
  dataRoot:
    storageClassName: <your-class>

On platforms where no default is created, this is also how the data root is provisioned in the first place.

Resize semantics, changing the class later, and the trade-offs of the cluster's built-in gp2 class are in the Operations reference. If the class encrypts with a customer-managed KMS key, the EBS CSI driver needs a KMS grant, exactly as for the created default.