Documentation for Deployment are outdated for both Kubernetes and Docker
- Dominant language
- Rust
- Stars
- 20.8k
- Forks
- 2.1k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 181
Description
First off, thank you for your awesome work done on this amazing product!
I struggle to follow the documentation for deployment as they are outdated for both kubernetes and docker. The examples that I could access like [kubernetes/cluster](https://github.com/cube-js/cube.js/tree/master/examples/kubernetes/cluster) are 11 months old and contain Enviroment variables that are either depricated or not applicable for newer S3 EXPORT config. Almost all examples in the repo and documentation still use CUBESTORE_REMOTE_DIR although this looks to be incorrect when looking at github issues and env docs that sates: Not required if using GCS/S3. Not recommended for production usage.
**There is a difference between env values generated with the newest cube-cli and the [documentation](https://cube.dev/docs/deployment/overview)**
Which configuration is the correct or preferred config, the documentation or cube-cli?
The following variables isn't even listed on [docs](https://cube.dev/docs/reference/environment-variables), but
is set when project structure is generated with cli :
```text
CUBEJS_EXTERNAL_DEFAULT=true
CUBEJS_SCHEDULED_REFRESH_DEFAULT=true
```
This discrepancies between ENV docs, Deployment Docs, old github repos and cli generated config seems to lead to confusion when I look at the issues logged related to this.
What should a basic setup look like when I want to make use of S3 cloud storage with CUBEJS_DB_EXPORT_BUCKET_TYPE=S3
Kind Regards
Johan
Contributor guide
Assessment
This issue has not been assessed yet.