Document conditions for upstream charts to be forked and changed
From 13 Mar 2018 meeting:
Use of upstream charts whenever possible #208 (closed) & #203 (closed)
- Any chart that is not required to be a local fork should be using upstream
- What exactly delineates “required” here? These need to be documented, based on the general rules for need to fork.
Charts that have upstream, but we’ve forked:
- Registry (docker-registry) for population of configuration and secrets, not via ENV
- Minio (minio) for additional bucket configuration, and secret population not via ENV
- Kube-lego (kube-lego), to be phased out for cert-manager!
- Redis (redis / redis-ha) was less forked, than re-created. Population of configuration and secrets, not via ENV
Edited by Jason Plum