Running securityadmin.sh in Kubernetes PODs

Security
1

Hi, I am installing OpenDistro ElasticSearch Helm Charts. I would like to avoid running securityadmin.sh against the PODs after containers are up and running. The documentation is a bit unclear. My understanding is that if all Secrets are defined and “opendistro_security.allow_default_init_securityindex” is enabled, then I don’t need to run securityadming.sh.

Can someone clarify if my understanding is correct ? Thank you !

2

@ppp That is correct, this can be tested using simple docker-compose file with necessary config files mapped via volumes to relevant containers. If the configuration is correct, the security index will initialise automatically and no further actions will be needed.
Hope this helps