Closed thomas-2020 closed 4 months ago
Please note that it works, 100% sure, and we have smoke tests on our helm charts ;-)
Just run as written in the README:
helm install <release-name> --set-file terracotta.license=<license-file> --set tag=4.3.10-SNAPSHOT
For example, we start our non-secured smoke tests with:
launch helm install "my-release" \
--set-file terracotta.license=license.key \
--set terracotta.stripeCount=2 \
--set terracotta.nodeCountPerStripe=2 \
--set terracotta.offHeapSize=512m \
--set terracotta.datastoreSize=512m \
--set registry=iregistry.eur.ad.sag \
--set serverImage=terracotta/bigmemorymax-server \
--set tmcImage=terracotta/bigmemorymax-tmc \
--set tag=$VERSION \
$helm_path
You have changed the layout of values.yaml
. Now is the value license
under terracotta
. With the last values.yaml
is the deployment successfully.
yes. this setting is bound to terracotta: this is a tc license key.
I use the license key inside values.yaml ...
The license.key file in ConfigMap is empty ...
(I am a little confused because this was already working)