Kubernetes Chart Questions
- Dominant language
- Rust
- Stars
- 20.8k
- Forks
- 2.1k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 181
Description
**Problem**
A couple of questions with the kubernetes chart:
1. according to https://cube.dev/docs/caching/running-in-production docs for cubestore
```
[CUBESTORE_WORKERS](https://cube.dev/docs/reference/environment-variables#cubestore-workers) and [CUBESTORE_META_ADDR](https://cube.dev/docs/reference/environment-variables#cubestore-meta-addr) variables should be set with stable addresses
```
since that is the case, would it not make more sense to just point the environment variables to the corresponding `service` rather than using headless services, etc.
Since if you want to horizontally scale cubestore workers, you do not need to recreate every single worker, since in the current scheme if you want to add a worker, you need to change the environment variable for all other workers to also include the new worker i.e. causing it to recreate all previous workers. Please let me know if there is a specific reason as to why this was not done
2. Why are cubestore workers set as statefulsets?
- are there any other reasons apart from convenience reasons i.e. it auto-creates persistent volumes for each worker
3. Do you really need persistence volumes?
- my understanding is that the cubestore workers utilises a scratch space for its local `CUBESTORE_DATA_DIR` whereas the `CUBESTORE_REMOTE_DIR` should be handled not natively to the pod anyways e.g. either a NFS / Blob storage.
- what is the relevance of persistent volumes re: cubestore workers, and is there an underlying logical reason as to why persistence volumes are preferred over plain ephemeral storage?
Thank you!
Contributor guide
Assessment
This issue has not been assessed yet.