How to scale beyond the cluster? #2468
Comments
|
Since multi-cluster work tends to be platform specific, you will need to implement this yourself for your specific platform. We do have https://agones.dev/site/docs/advanced/multi-cluster-allocation/, although that doesn't answer your specific question. |
|
'This issue is marked as Stale due to inactivity for more than 30 days. To avoid being marked as 'stale' please add 'awaiting-maintainer' label or add a comment. Thank you for your contributions ' |
github-actions
bot
added
the
stale
|
Bumping out of stale. Area of research internally, will share some ideas for discussion when complete. |
|
'This issue is marked as Stale due to inactivity for more than 30 days. To avoid being marked as 'stale' please add 'awaiting-maintainer' label or add a comment. Thank you for your contributions ' |
github-actions
bot
added
the
stale
|
This issue is marked as obsolete due to inactivity for last 60 days. To avoid issue getting closed in next 30 days, please add a comment or add 'awaiting-maintainer' label. Thank you for your contributions |
|
@gongmax did you want to keep this open? |
github-actions
bot
removed
obsolete
stale
|
'This issue is marked as Stale due to inactivity for more than 30 days. To avoid being marked as 'stale' please add 'awaiting-maintainer' label or add a comment. Thank you for your contributions ' |
github-actions
bot
added
the
stale
markmandel
added
awaiting-maintainer
|
Keeping this open! |
Offline we tend to recommend people use a Service Mesh for multi-cluster allocation, but I keep seeing people running into our docs and trying to implement our solution. Rather than waiting on a full investigation and documentation, I wanted to put a note at the top making a recommendation to go in a different direction - so that people don't actively chase this path if they aren't aware there are other (better) paths for multi-cluster communications. Work on googleforgames#2468
Offline we tend to recommend people use a Service Mesh for multi-cluster allocation, but I keep seeing people running into our docs and trying to implement our solution. Rather than waiting on a full investigation and documentation, I wanted to put a note at the top making a recommendation to go in a different direction - so that people don't actively chase this path if they aren't aware there are other (better) paths for multi-cluster communications. Work on #2468 Co-authored-by: Robert Bailey <[email protected]>
I'm new to kubernetes/docker, so I apologize if I use any wrong terms here. I plan on hosting this on Linode as the costs of GCP/AWS is just too high in comparison. Linode has a limit of 100 nodes per cluster from what I am reading in their documentation.
How do you manage auto scaling beyond one cluster using Agones, or is that not possible?
Would we need to keep an eye on if a cluster is starting to get full and then install another instance of Agones on a new cluster?
The text was updated successfully, but these errors were encountered: