Use local-volume-provisioner for Managed Services that requires high-speed disks.¶
- Status: accepted
- Deciders: arch meeting
- Date: 2022-11-10
Context and Problem Statement¶
After performing several storage load testing and PostgreSQL load testing and benchmarking we have discovered that the local storage is significantly faster than network storage. We have one use case where the disk have proven to be too slow for a PostgreSQL database and the performance was not as expected. How should we expose local storage to Managed Services?
- We want to best serve the Application Developer needs.
- We want to offer fast performant Managed Services.
- We want to find a solution which is scalable and minimizes administrator burden.
- We want to find a future-proof solution, which exposes local disks to any application.
- Use the fastest network storage with dedicated IOPS.
- Use local storage with local-volume-provisioner.
- Use local storage with local-path-provisioner
- Use hostPath
- Use local
Chosen option: Use local storage with local-volume-provisioner and move the code within the kubespray repo.
- Services using the local storage are performing better.
- We are able to provide a PostgreSQL service that meet the high performance requirements.
- Scaling the storage becomes harder as it will involve replacing the nodes.
- We are limited by the size of the volumes that are available within the Infrastructure Provider offering.
Recommendation to Platform Administrators¶
When using the local-volume-provisioner please create dedicated partitions and make sure to reserve enough space for the boot partition. Failing to do so can lead to entire disc to become full and the node will become unresponsive and crash.