Migrate Space Agon to OM2 (Running OM2 on GKE) #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up PR that migrate Space Agon from using OM1 to OM2. This PR deploys OM2 on GKE instead of on Cloud Run. Due to limited time, I didn't use helm chart, and simply wrote the om_install.yaml and redis-config.yaml files to deploy OM2.
To run the demo, follow the README until you finished installing Agones. Then to install OM2 to the cluster, in the root directory, first deploy the redis service with
and then change the
OM_CORE_IMAGE
field inside of om_install.yaml to be the OM2 image url - it can either beasia-northeast1-docker.pkg.dev/open-match-dev/open-match/om-core
if you have access to theopen-match-dev
project, or the URL of the OM2 image you build and upload to your own Artifact Registry by following the DEVELOPMENT.md. After changing theOM_CORE_IMAGE
field, deploy the OM2 service withThen proceed to install the Space Agon game with
make build && make install
.