Infinispan 13.0 allows the server and logging to be configured via yaml. Instead of utilising the _infinispan.xml and _log4j2.xml templates, we can embed the default configurations in the values.yaml.
The advantage of this approach is that it's now possible to update the configurations at chart creation time without having to modify any templates. This is necessary in order to better integrate with the Openshift Helm charts UI.
For example, values.yaml could like the following:
A consequence of this approach is that it's no longer possible to support the toggling of authentication (values.security.authentication: true | false) as template logic is not allowed in values.yaml.
Infinispan 13.0 allows the server and logging to be configured via yaml. Instead of utilising the
_infinispan.xml
and_log4j2.xml
templates, we can embed the default configurations in thevalues.yaml
.The advantage of this approach is that it's now possible to update the configurations at chart creation time without having to modify any templates. This is necessary in order to better integrate with the Openshift Helm charts UI.
For example,
values.yaml
could like the following:A consequence of this approach is that it's no longer possible to support the toggling of authentication (
values.security.authentication: true | false
) as template logic is not allowed invalues.yaml
.