Closed aimuz closed 2 months ago
That's curious, for sure. And there's nothing that could have triggered the game server itself to call Shutdown() (simultaneously)?
No call, He is concentrated around 10:00 Eastern time, around 2:00 UTC
A new day reappeared, it seems that the problem appeared when I upgraded to 1.30, I forget what version I belonged to before
```text ➜ ~ date Thu May 11 09:43:04 CST 2023 ➜ ~ kubectl -n pg-core get gs NAME STATE ADDRESS PORT NODE AGE battle-server-mlgmp-4ljq5 Ready 10.77.0.215 7176 worker03 3m50s battle-server-mlgmp-dq25q Ready 10.77.0.215 7153 worker03 3m50s battle-server-mlgmp-hxkzk Ready 10.77.0.215 7094 worker03 3m50s battle-server-mlgmp-rkl5s Ready 10.77.0.215 7144 worker03 3m50s battle-server-mlgmp-tdpk2 Ready 10.77.0.215 7023 worker03 3m50s ➜ ~ ➜ ~ ➜ ~ ➜ ~ ➜ ~ kubectl -n pg-core-test get gs NAME STATE ADDRESS PORT NODE AGE battle-server-8kq7r-75v95 Ready 10.77.0.215 7563 worker03 4m7s battle-server-8kq7r-cswz7 Ready 10.77.0.215 7322 worker03 8s battle-server-8kq7r-l7ddv Ready 10.77.0.215 7691 worker03 4m8s battle-server-8kq7r-mgqrg Ready 10.77.0.215 7785 worker03 4m8s battle-server-8kq7r-pc7jb Ready 10.77.0.215 7316 worker03 4m8s battle-server-8kq7r-tgrsl Allocated 10.77.0.215 7922 worker03 4m8s ```
Did a node do a Kubernetes version upgrade?
As far as I know no operations have been done and the problem has not occurred in the last few days
Probably too late, but would be interesting to see the Pod or Node events - that would probably give us a better idea on why the Pod was shutdown.
When I find the problem again, I'll add the pod and node-related events
'This issue is marked as Stale due to inactivity for more than 30 days. To avoid being marked as 'stale' please add 'awaiting-maintainer' label or add a comment. Thank you for your contributions '
This issue is marked as obsolete due to inactivity for last 60 days. To avoid issue getting closed in next 30 days, please add a comment or add 'awaiting-maintainer' label. Thank you for your contributions
What happened:
Without doing any updates, all my gs are restarted and the age is the same
What you expected to happen:
Curious as to why this is happening, is this a bug or a feature?
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): v1.24.6