Closed patricklucas closed 4 years ago
helm install --upgrade
in the PR description was a typo, I'll fix it.upgrade --install
and values file changes separate as that would reduce the "atomicity" of the commit. The reason for the whole change is those two things together and it's clear from the commit message what's going on.I split the first commit into:
commit 4c0b0e21d61d184f5a7a8f466b628f9358fb5f23
Minor chart values optimizations
- Allow Elasticsearch to run as a non-privileged container by disabling
its requirement for sysctl vm.max_map_count >= 262144
- Specify an (unused) admin password for Grafana so that it does not
regenerate its Kubernetes Secret on every upgrade which causes a
needless restart
commit 35565726f028710ad993da1964d6217121e94f50
Minor shell optimizations
Remove a function param to make calls a bit more explicit and remove
some code duplication.
commit ea5a4019102831c9795a140e333204b30e035f56
Allow enabling metrics/logging without teardown
By always activating the Prometheus metrics reporter and by using `helm
install --upgrade`, the setup script can be run multiple times
idempotently to enable logging and/or metrics without first tearing down
the existing installation.
By always activating the Prometheus metrics reporter and by using
helm upgrade --install
, the setup script can be run multiple times idempotently to enable logging and/or metrics without first tearing down the existing installation.Another side-effect of using
helm upgrade --install
is that we don't actually have to do Helm version discovery insetup.sh
anymore.