Hi, Using this example on how to enable custom logging using a ConfigMap, https://github.com/arkmq-org/activemq-artemis-operator/blob/main/examples/artemis/artemis_custom_logging_configmap.yaml
I can add the ConfigMap and describe it, but when I restart the Artemis broker pod I see that it is still using the default logging configuration built into the image. What debug steps should I take to find out why it is not picking up my logging config from the ConfigMap. I am also using a custom init image that we use to have a custom JAAS securityManger used by the broker. I don’t know if that would interfere with recognizing the ConfigMap? I am using Artemis 2.34.0 and operator 1.2.2, Does this version support the ConfigMap feature? fssrv:~ # kubectl -n dvs get configmaps NAME DATA AGE dvs-activemq-artemis-operator-config 1 2y200d d864aab0.amq.io 0 2y200d istio-ca-root-cert 1 2y348d kube-root-ca.crt 1 2y348d log4j-properties-logging-config 1 3d19h
