v10.0.2-alpha

Fixed

• Runtime watcher uses multiple goroutines to process kubernetes events

V10.0.1

Changed

• Runtime watcher channel size from 100 to 2000

V10.0.0

• Stable version for Maestro Next

v10.0.0-rc24

Changed

• Change RoomsAPI Status handler to treat ping from game rooms

v10.0.0-rc23

Added

Create new patch scheduler feature so users can update single or multiple fields of the given scheduler.
PATCH /schedulers/:schedulerName

v10.0.0-rc22

Fixed

• metadata["ports"] were being forwarded in the wrong format
• scheduler.spec.container[].command could not be empty

v10.0.0-rc21

Added

• Map error type "operation canceled" for operations
• GET /scheduler/:schedulerName/operations/:operationId endpoint

Fixed

• Add-rooms rollback not working properly
• Port allocator logic was conflicting on adding rooms

Changed

• e2e tests running in parallel

v10.0.0-rc20

Added

• Basic documentation to maestro docs

Changed

• Change method ping from POST to PUT (because of Maestro-client);

Fixed

• Remove watcher unreadable log

v10.0.0-rc19

Added

• Adds support to valueFrom.

Fixed

• Operation canceled breaks rollback routine;
• Review errors that are been added to execution history;
• Memory leak on rooms API.

v10.0.0-rc18

Added

• Metrics for tracking Redis error rate and response time;
• Metrics for tracking events forwarding error rate and response time;
• Games label to Maestro Metrics

Fixed

• When an operation fails, execution history does not contain error message;
• Error cannot create new scheduler version.

Improvements

• Clean named and anonymous container volumes after running e2e tests