Closed enginsarlak closed 2 months ago
Sorry, it seems to be that MSR needs always a LK.
LK? Does it mean I can't use these helm charts with integration server license alone? Is there a workaround I can apply?
Has you created your own MSR/IS image? Then you need always a license key (LK). The MSR image in containers.softwareag.com
has an own Trail license. Only in this case is --set microservicesruntime.licenseKeyProvided=false
working.
microservicesruntime.licenseKeyProvided=false
is working only with the MSR image which is provided on containers.softwareag.com
IS container expects MSR license to inject application.properties file. Steps to reproduce, Update the MSR repo url to IS container repo. Add license file as indicated in helm readme (as config map). Helm install using a license without MSR capabilities.
As recommended, setting/adding the parameter
--set microservicesruntime.licenseKeyProvided=false
made container work but it made it start with a trial license, not the license I have provided. The trial license is set to expire in 90 days so this workaround doesn't work for me.Is there a way to keep using values.yaml file and IS containers with these helm charts?
Related container logs are attached below.