You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying an Elasticsearch cluster through ECK, are there any recommendations for the number of clusters managed by a single elastic-operator?
One operator instance can manage several hundred of clusters. Its capacity is mostly bound by the resources allocated to it and the limitations of the underlying Kubernetes installation. Check #357 (comment).
If you need to manage a large number of clusters, monitor memory usage and adjust the container resources as necessary. You should also increase max-concurrent-reconciles to handle multiple resources at the same time.
If there are many clusters, do they need to be deployed in multiple namespaces and managed using different elastic-operators?
Not necessarily, it's up to you how you want to organize your Elastic deployments based on your use case. Just make sure you don't have 2 operators managing the same namespace.
Please reserve GitHub issues exclusively for bug reports and feature requests directly related to the ECK operator. You can ask these kinds of questions in our community support forum https://discuss.elastic.co/c/orchestration/eck/79. Thank you.
When deploying an Elasticsearch cluster through ECK, are there any recommendations for the number of clusters managed by a single elastic-operator?
If there are many clusters, do they need to be deployed in multiple namespaces and managed using different elastic-operators?
The text was updated successfully, but these errors were encountered: