SoftwareAG / webmethods-helm-charts

This repository contains a collection of Helm charts for various webMethods components.
https://open-source.softwareag.com/webmethods-helm-charts/
Apache License 2.0
8 stars 14 forks source link

License not in ConfigMap #59

Closed thomas-2020 closed 4 months ago

thomas-2020 commented 4 months ago

I use the license key inside values.yaml ...

...
# -- Create a secret manually in cluster which contains all the necessary certs, files etc. for all the servers as well as tmc as the same secret will be mounted to all the pods deployed via this helm chart.
secretName:
# -- The license content for the Terracotta cluster. Required.
license: |
  Date of Issue: 2023-11-22
  Expiration Date: 2026-12-10
...

The license.key file in ConfigMap is empty ... image

(I am a little confused because this was already working)

mathieucarbou commented 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
thomas-2020 commented 4 months ago

You have changed the layout of values.yaml. Now is the value license under terracotta. With the last values.yaml is the deployment successfully.

mathieucarbou commented 4 months ago

yes. this setting is bound to terracotta: this is a tc license key.