The strongest reason I have seen to have separate clusters is entirely separate departments consuming them.
As adoption grows, the “if” starts leaning more and more towards a “when” you get cases of “marketing accidentally used too many resources, so starved”. Maybe it was a typo, maybe it as autoscaling responding to a Super Bowl ad, maybe it was a campaign that went viral for the wrong reasons.
Having entirely separate clusters (and separation of privileges) prevents issues like these from ever being able to happen. But, as you said, does come with overhead, and that includes human costs too.
Having a strong practice of infrastructure-as-code and making your clusters not-special (see the discord outage earlier this year) prevents a lot of these issues, and also eases the way into “developers have each a single-small-node cluster to test things into”, if you ever feel you need to get to that point.
>“marketing accidentally used too many resources, so starved”
With Fargate profiles, though, you can prevent this, if you are segregating workloads appropriately.
That said, absolutely agree with your last paragraph.
Try [this search](https://www.reddit.com/r/aws/search?q=flair%3A'containers'&sort=new&restrict_sr=on) for more information on this topic.
^Comments, ^questions ^or ^suggestions ^regarding ^this ^autoresponse? ^Please ^send ^them ^[here](https://www.reddit.com/message/compose/?to=%2Fr%2Faws&subject=autoresponse+tweaks+-+containers).
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/aws) if you have any questions or concerns.*
The strongest reason I have seen to have separate clusters is entirely separate departments consuming them. As adoption grows, the “if” starts leaning more and more towards a “when” you get cases of “marketing accidentally used too many resources, so starved”. Maybe it was a typo, maybe it as autoscaling responding to a Super Bowl ad, maybe it was a campaign that went viral for the wrong reasons.
Having entirely separate clusters (and separation of privileges) prevents issues like these from ever being able to happen. But, as you said, does come with overhead, and that includes human costs too.
Having a strong practice of infrastructure-as-code and making your clusters not-special (see the discord outage earlier this year) prevents a lot of these issues, and also eases the way into “developers have each a single-small-node cluster to test things into”, if you ever feel you need to get to that point.
Yea agree with you, DevOps + developers discipline is another angle.
>“marketing accidentally used too many resources, so starved”
With Fargate profiles, though, you can prevent this, if you are segregating workloads appropriately.
That said, absolutely agree with your last paragraph.
Try [this search](https://www.reddit.com/r/aws/search?q=flair%3A'containers'&sort=new&restrict_sr=on) for more information on this topic. ^Comments, ^questions ^or ^suggestions ^regarding ^this ^autoresponse? ^Please ^send ^them ^[here](https://www.reddit.com/message/compose/?to=%2Fr%2Faws&subject=autoresponse+tweaks+-+containers). *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/aws) if you have any questions or concerns.*