Summary/Description
We currently have a Docker compose workflow that's used for both local development, testing, and exploration. However, most folks aren't using Docker Compose for production deployments (I hope). The upstream Superset repository offers a Helm deployment. It would be nice to offer something similar using Kustomize.
Why Kustomize?
Helm and Kustomize accomplish the same thing but Kustomize is much easier to read because it does not use the bracketed templating syntax. Readability wins in my opinion.
Proposed Solution
Add a kustomization directory at the root of the repo containing the Kustomize artifacts for deploying GeoSet. We could offer multiple overlays corresponding to lean, production, etc.
Summary/Description
We currently have a Docker compose workflow that's used for both local development, testing, and exploration. However, most folks aren't using Docker Compose for production deployments (I hope). The upstream Superset repository offers a Helm deployment. It would be nice to offer something similar using Kustomize.
Why Kustomize?
Helm and Kustomize accomplish the same thing but Kustomize is much easier to read because it does not use the bracketed templating syntax. Readability wins in my opinion.
Proposed Solution
Add a
kustomizationdirectory at the root of the repo containing the Kustomize artifacts for deploying GeoSet. We could offer multiple overlays corresponding to lean, production, etc.