What happened:
I'm using open-match 1.8.0 and when I set open-match-scale.enabled to true, the frontend component's cpu and memory
would go up.
If open-match-scale is not installed, this will not happen
kubectl top pod -n open-match|grep open-match-frontend
open-match-frontend-6568f8dc75-9tc9b 98m 276Mi
Events:
Type Reason Age From Message
Normal Scheduled 26m default-scheduler Successfully assigned open-match/open-match-frontend-6568f8dc75-9tc9b to cn-hangzhou.192.168.0.129
Normal AllocIPSucceed 26m terway-daemon Alloc IP 192.168.0.141/18 took 53.198108ms
Normal Created 26m kubelet Created container open-match-frontend
Normal Started 26m kubelet Started container open-match-frontend
Warning Unhealthy 22m (x3 over 22m) kubelet Liveness probe failed: Get "http://192.168.0.141:51504/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Normal Killing 22m kubelet Container open-match-frontend failed liveness probe, will be restarted
Warning Unhealthy 22m (x13 over 26m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
Warning Unhealthy 11m (x6 over 22m) kubelet Readiness probe failed: Get "http://192.168.0.141:51504/healthz?readiness=true": dial tcp 192.168.0.141:51504: connect: connection refused
Warning BackOff 6m42s (x19 over 22m) kubelet Back-off restarting failed container open-match-frontend in pod open-match-frontend-6568f8dc75-9tc9b_open-match(9be4111f-b783-45dc-824c-570e2ae74565)
Warning Unhealthy 102s (x40 over 22m) kubelet Readiness probe failed: Get "http://192.168.0.141:51504/healthz?readiness=true": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
What happened: I'm using open-match 1.8.0 and when I set open-match-scale.enabled to true, the frontend component's cpu and memory would go up. If open-match-scale is not installed, this will not happen
kubectl top pod -n open-match|grep open-match-frontend open-match-frontend-6568f8dc75-9tc9b 98m 276Mi
Events: Type Reason Age From Message
Normal Scheduled 26m default-scheduler Successfully assigned open-match/open-match-frontend-6568f8dc75-9tc9b to cn-hangzhou.192.168.0.129 Normal AllocIPSucceed 26m terway-daemon Alloc IP 192.168.0.141/18 took 53.198108ms Normal Created 26m kubelet Created container open-match-frontend Normal Started 26m kubelet Started container open-match-frontend Warning Unhealthy 22m (x3 over 22m) kubelet Liveness probe failed: Get "http://192.168.0.141:51504/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 22m kubelet Container open-match-frontend failed liveness probe, will be restarted Warning Unhealthy 22m (x13 over 26m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503 Warning Unhealthy 11m (x6 over 22m) kubelet Readiness probe failed: Get "http://192.168.0.141:51504/healthz?readiness=true": dial tcp 192.168.0.141:51504: connect: connection refused Warning BackOff 6m42s (x19 over 22m) kubelet Back-off restarting failed container open-match-frontend in pod open-match-frontend-6568f8dc75-9tc9b_open-match(9be4111f-b783-45dc-824c-570e2ae74565) Warning Unhealthy 102s (x40 over 22m) kubelet Readiness probe failed: Get "http://192.168.0.141:51504/healthz?readiness=true": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Open Match Release Version: 1.8.0
Install Method(yaml/helm) helm