v10.11.4

fix: try create occupancy key to existing rooms (#659)

v10.10.6

• fix(runtime-watcher): do not exit disruption goroutine on errors

Unerecoverable errors are normal when updating PDB, for instance k8s might be updating at the same time, or we get throttled by Kube API, or we simply fail to get from Redis. In either way, if we return/exit we don't close the watcher since there's another goroutine running, leaving to scenarios that watcher is running only game room events loop. For now, if disruption failed, we log and retry in the next loop

Also:

• fix(runtime-watcher): make Stop() indempotent

• fix(runtime-watcher): default disruption loop to 60s

Previously the mitigate disruption loop that updates PDB was running
every 5s, changing to 60s. Also, moved the logs to INFO so we can track
this in production, one log entry per scheduler per min shouldn't spam
the logs

Full Changelog: v10.10.5...v10.10.6

v10.11.3

What's Changed

• fix: remove scheduler earlier validation when patching it by @reinaldooli in #657
• fix(runtime-watcher): do not exit disruption goroutine on errors by @hspedro in #658

Full Changelog: v10.11.1...v10.11.3

v10.11.2

fix: remove scheduler earlier validation when patching it

v10.11.1

fix: downscale calculation considering matches (#656)

v10.11.0

Full Changelog: v10.10.5...v10.11.0

v10.11.0-alpha.12

fix: sync scheduler before sending metrics

v10.11.0-alpha.11

feat: report metric with scheduler max matches

v10.11.0-alpha.9

fix: adding transition from occupied to active

v10.11.0-alpha.10

fix: multiple matches status calculation