Please forgive me if this specific topic has already been discussed elsewhere, I couldn't find much information matching what I'm looking for.
I'm managing EFK stacks across multiple Kubernetes clusters and while the deployment of the various EFK components is fully automated in my environment using Helm charts and our CI/CD pipeline, many of the configuration aspects of Elasticsearch and Kibana I'm having difficulty managing.
One of those difficulties is around ILM and programmatically configuring the index template. While I can create and manage this using the API, it can be cumbersome in our environment to have to go through these manual steps for each new Kubernetes cluster we create or recreate. Is there currently any way or any plans in the future to allow this to be done in an automated fashion?
I'm thinking similar to how certain attributes can be defined in the elasticsearch.yml and log4j2.properties files which we're able to define in our Helm chart values.yml files for Elasticsearch. By allowing for this, each time a new Kubernetes cluster is spun up, the index template we have defined whill in turn be created on each Elasticsearch node and match across the entire Elasticsearch cluster.
If I'm missing something or not understanding any reason that this can't be done, I'm all ears. If anybody has done something to automate this themselves such as configuring a CronJob to make the API call to create those index templates upon cluster creation that would be great as well though I'm a bit junior in my skills in this area.