Elastic Stack Config Policy: etcd object size limit limits the size of the Stack config policies

[TimBosman]

Right now, it is not possible to add multiple Elastic Stack Config Policy to one Elasticsearch cluster. This means that the amount of things to configure is limited by the etcd object size limit. I see two options to avoid this problem:

• Making it possible to add multiple Elastic Stack Config Policies to one Elasticsearch Cluster.
• Making it possible to reference to Kubernetes configmaps or secrets containing the configuration from the Elastic Stack Config Policy.

[thbkrkr]

That's true but the size is 1.5MB? Have you reached it?

[TimBosman]

I've created this issue after customer feedback. They told me they have hit the limit.

[pebrc]

As @barkbay has pointed out the issue here is that even if we were to allow multiple config policies that the resulting configuration still needs to fit into a single Kubernetes API object in order for us to be able to mount it into the Elasticsearch Pods.

[mtparet]

We could concat multiple configuration within elasticsearch pods ?

[thbkrkr]

We could concat multiple configuration within elasticsearch pods ?

The problem I see with this is how do I keep the concatenation in sync every time a configuration is updated?

Today, the file containing the Elastic Stack configuration policy settings presented to ES is mounted from a Secret. When the Stack config policy is updated, the associated Secret is updated, and so, the file is updated in the pod and ES hot reloads the new configuration from the file, without restart.

[mtparet]

We could have a side container doing concatenation and writing the concatenated file. But the proper way seems to be adding support for a folder-based files settings inside Elasticsearch.