Refactor Harness Chart to use Helm Best Practices
Progress Tracking
-
parent chart -
access-control -
change-data-capture -
ci -
gateway -
harness-manager -
harness-storage-proxy -
log-service -
minio -
mongo -
next-gen-ui -
ng-auth-ui -
ng-manager -
pipeline-service -
platform-service -
redis -
scm-service -
template-service -
test-intelligence-service -
timescaledb
Notes
This involves createing a chart using helm create
and porting the existing orchestration to the manifests created there as well as following best practices for manifests/keys not covered. For example, secrets and configmaps need to not be hardcoded and be settable through values.
Edited by Jordan McClintock