Operator does not reload when SmbShare's settings are changed about samba-operator

[phlogistonjohn]

To help identify the issue: can you please take a look at the generated configmap that the operator creates and see if the change is reflected in the generated JSON file there that the operator provides to the samba containers?

[pfaelzerchen]

The changes are immediately reflected in the config map. Switching to readOnly true, kubectl apply and kubectl get cm shows "read only": "yes" in the config map. This is also completely reproducible (switching back and forth).

[phlogistonjohn]

That implies that the problem is on the samba container side. Either an issue in the interaction between the configmap and the container or a bug in sambacc. Thanks for the info - I'll try and look into it more in-depth soon.