# Suggestions on what Large test cluster footprint might look like? **URL:** \ **Category:** Elasticsearch\ **Created:** [October 16, 2020, 6:54pm UTC](https://discuss.elastic.co/t/suggestions-on-what-large-test-cluster-footprint-might-look-like/252388 "2020-10-16T18:54:24Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![rgeisman](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@rgeisman](https://discuss.elastic.co/u/rgeisman)\ **Post date:** [October 16, 2020, 6:54pm UTC](https://discuss.elastic.co/t/suggestions-on-what-large-test-cluster-footprint-might-look-like/252388/1 "2020-10-16T18:54:24Z")
Hello all. Great conference by the way. Excellent question answer sessions and breakout talks. One question I wanted to ask is that I have setup an ELK stack to monitor 1000+ nodes with filebeat, metricbeat, Suricata and Packetbeat. In production we have 5 Elasticsearch boxes with Logstash consuming beats and everything works great. But, we need a test cluster. It would be very beneficial to have a cluster where I could test upcoming logstash configuration changes which entail bouncing the instance, making template changes, hot/cold storage configs, etc. What is a good approach to building a low cost test cluster? Might sound nuts, but could you take something like K8's and then spin up 1000 or so VM's and an ELK Cluster? Would a certain fraction of the VM's be sufficient for testing... Just an overall question of what test cluster footprints look like and typical deploy strategies between them? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 13, 2020, 6:54pm UTC](https://discuss.elastic.co/t/suggestions-on-what-large-test-cluster-footprint-might-look-like/252388/2 "2020-11-13T18:54:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.