Overview
When sizing a GKE ComputeClass for self-hosted SmithDB nodes, it's easy to conflate the node's boot disk size with the storage SmithDB uses for its /data cache. Example manifests sometimes set a very large bootDiskSize (for example 1,500 GiB on a hyperdisk-balanced disk) as a cautious placeholder before Local SSD-backed storage has been confirmed. That large value is not a SmithDB requirement.
Details
bootDiskSize in a ComputeClass sizes the node's OS boot disk. SmithDB's cache capacity is a separate concern, controlled by smithdb.resourceTier and the per-component cache size it resolves to. These two settings aren't linked, so a node doesn't need a large boot disk just because SmithDB needs a large cache.
A 100 GiB boot disk is adequate for SmithDB nodes. The boot disk only needs to hold the OS image and supporting files, not cache data.
SmithDB's cache should be backed by Local SSD-backed ephemeral storage, not the boot disk. When the cache is configured as an emptyDir volume, its size limit comes from the container's limits.ephemeral-storage, which must be set explicitly for caching on Local SSD. Starting with chart version 0.17, SmithDB defaults its cache volumes to per-pod ephemeral PVCs; using Local SSD-backed emptyDir for the cache requires an explicit override rather than being inferred automatically from picking a Local-SSD-equipped machine type.
Verifying the cache is on Local SSD
Before reducing a boot disk on an existing ComputeClass, confirm the SmithDB cache is actually backed by Local SSD-backed ephemeral storage and not conflated with the boot disk:
Check the node pool's Local SSD ephemeral storage configuration.
Check the node's allocatable
ephemeral-storage.Check the filesystem backing
/dataon a running SmithDB pod.
Once that's confirmed, the boot disk can be sized for the OS and image only, independent of cache capacity.