Improve support of Amazon EKS production grade deployments

[sdpoueme]

Is your feature request related to a problem? Please describe.
Many customers looking to run Agones game servers are facing challenges with setting up and managing these components on Amazon EKS. This is becoming a common requirement for building end-to-end game server hosting solutions that can integrate with the AWS ecosystem.

Describe the solution you'd like
We propose the following feature addition to the Agones project:

1. Improved support for Amazon EKS multi-cluster and multi-region game server deployments, including enhancements to ingress mechanisms, allocation and load balancing of game sessions across geographically distributed Agones clusters on AWS.
2. Terraform-based Infrastructure as Code (IaC) to simplify the deployment and management of Agones-based game server fleets on Amazon EKS.

Describe alternatives you've considered
Manuel setup and configurations. But this is very tedious. Using Helm works, but requires customization and a certain level of knowledge regarding potential parameters to setup.

Additional context
The approach we propose is an approach based on AWS best practices and a fully vetted solutions architecture guidance.

[sdpoueme]

Here is the list of proposed changes. Most of the contributions will derive from the work done in AWS Solution Guidance for Agones and OpenMatch on EKS

• Update Agones docs https://github.com/googleforgames/agones/tree/main/docs
  • Update EKS installation steps
  • Add steps to enable observability on the cluster and upload the Grafana dashboard
• Add examples in the examples folder https://github.com/googleforgames/agones/tree/main/examples
  • Update the EKS Terraform module https://github.com/googleforgames/agones/blob/main/examples/terraform-submodules/eks/module.tf
• Update the install steps for EKS
  • Update the Terraform definition for EKS https://github.com/googleforgames/agones/tree/main/install/terraform/modules/eks
• Include extensions for shell scripts in the command folder https://github.com/googleforgames/agones/tree/main/cmd
  • Convert all shell scripts built in the solution guidance to Go scripts
  • Create a folder for EKS scripts
• Include a Grafana dashboard for EKS based on CloudWatch Container Insights

[markmandel]

Include extensions for shell scripts in the command folder https://github.com/googleforgames/agones/tree/main/cmd

What shell scripts are you talking about in here?

[sdpoueme]

The shell scripts we are referring to are the ones we built to finalize the setup of the eks cluster and perform sanity checks. Our plan is to move them to go and add them to the cmd folder.

[markmandel]

Not sure if that's the right spot for general usage scripts (the cmd folder is for Agones binaries) 🤔 not sure if we have a spot for that. Feels almost like those scripts should be maybe done as either part of Terraform, or maybe as a Helm test kind of thing? (I'm still not 100% sure of their need - but that could be a problem for another day).

But generally our installation stuff goes in https://github.com/googleforgames/agones/tree/main/install

[github-actions]

'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 '