We faced the issue that our edited security.json was suddenly replaced by the setup-zk with the initial bootstrap security.json version and the client application was not able to connect to Solr cluster anymore.
There were some instabilities & connection issues at zookeeper side that caused the command sequence from the init container:
ZK_SECURITY_JSON=$(/opt/solr/server/scripts/cloud-scripts/zkcli.sh -zkhost ${ZK_HOST} -cmd get /security.json);
failed with a connection timeout
but the afterwards executed "put security.json in ZK" succeeded.
We faced the issue that our edited security.json was suddenly replaced by the setup-zk with the initial bootstrap security.json version and the client application was not able to connect to Solr cluster anymore.
There were some instabilities & connection issues at zookeeper side that caused the command sequence from the init container:
ZK_SECURITY_JSON=$(/opt/solr/server/scripts/cloud-scripts/zkcli.sh -zkhost ${ZK_HOST} -cmd get /security.json);failed with a connection timeout but the afterwards executed "put security.json in ZK" succeeded.