v0.7.0
This is the 0.7.0 release of Open Match.
Check the README for details on features, installation and usage.
Release Notes
Feature Highlights
- Added filtering based on string and boolean values.
- Return all tickets when no filters are specified.
- Improved scaling.
- Supported payload logging.
Breaking Changes - Previous releases are not compatible with this release.
- Changed several gRPC and HTTP endpoints from unary to streaming to improve system scalability. #739
- Changed protobuf namespace from
apitoopenmatch. - Renamed protobuf
FiltertoFloatRangeFilter.
See https://open-match.dev/site/swaggerui/index.html. Future releases towards 1.0.0 may still have breaking changes.
Security Fixes
- None
Enhancements
- Payload logging now is available if debug/trace level logging is turned on. #696
- New filtering mechanism. #681
- Improved synchronizer logging to avoid log spam. #784
- Serveral API changes from unary to streaming. #739
- New Continuous Integration pipeline with faster build time for Open Match developers. #701
- New Helm subchart to deploy customized evaluators and match functions. #652
- New package to benchmark and scale testing Open Match. #797
- Documentation on how to access Open Match under different cluster settings. open-match-docs#43
- Documentation on how to use Open Match via HTTP/gRPC endpoints. open-match-docs#41
Images
# Servers
docker pull gcr.io/open-match-public-images/openmatch-backend:0.7.0
docker pull gcr.io/open-match-public-images/openmatch-frontend:0.7.0
docker pull gcr.io/open-match-public-images/openmatch-mmlogic:0.7.0
docker pull gcr.io/open-match-public-images/openmatch-synchronizer:0.7.0
# Evaluators
docker pull gcr.io/open-match-public-images/openmatch-evaluator-go-simple:0.7.0
# Sample Match Making Functions
docker pull gcr.io/open-match-public-images/openmatch-mmf-go-soloduel:0.7.0
docker pull gcr.io/open-match-public-images/openmatch-mmf-go-pool:0.7.0
# Test Clients
docker pull gcr.io/open-match-public-images/openmatch-demo-first-match:0.7.0This software is currently alpha, and subject to change. Not to be used in production systems.
Installation
To deploy Open Match in your Kubernetes cluster run the following commands:
# Grant yourself cluster-admin permissions so that you can deploy service accounts.
kubectl create clusterrolebinding myname-cluster-admin-binding --clusterrole=cluster-admin --user=$(YOUR_KUBERNETES_USER_NAME)
# Place all Open Match components in their own namespace.
kubectl create namespace open-match
# Install Open Match and monitoring services.
kubectl apply -f http://open-match.dev/install/v0.7.0/yaml/install.yaml -n open-match
# Install the demo.
kubectl apply -f http://open-match.dev/install/v0.7.0/yaml/02-open-match-demo.yaml -n open-matchAPI Definitions
https://open-match.dev/api/v0.7.0/backend.swagger.json
https://open-match.dev/api/v0.7.0/evaluator.swagger.json
https://open-match.dev/api/v0.7.0/frontend.swagger.json
https://open-match.dev/api/v0.7.0/matchfunction.swagger.json
https://open-match.dev/api/v0.7.0/mmlogic.swagger.json