I’ve posted a design doc on how we could support multiple storage servers per disk in the Kubernetes Operator. If anyone is interested in this area, I’d love your feedback on the proposed design.
2 Likes
We tried the feature in our deployment, but facing a dilemma on resource provision. We would like to give more CPU and memory to the storage server pod with multiple storage servers, but that will introduce redundancy for other pods (resolver, stateless, etc.) since all pod share same pod template to for resource specification.
Is there a way to specify custom template for different class of pod? Could not find it, but would really helpful if this is something that could be overridden on each pod type, or the multiple storage server would be limited due to insufficient CPU/memory.
You can set different Pod templates for different processes you just have to add an additional Pod template with the “storage” key. We have some documentation about that here: fdb-kubernetes-operator/customization.md at master · FoundationDB/fdb-kubernetes-operator · GitHub, the example with different PVC templates for log and storage processes.