You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
With Kubernetes 1.24, GKE will no longer be supporting node images with the dockershim runtime, which includes windows_ltsc (the image currently used in our windows instructions).
Describe the solution you'd like
We should switch to a node image with the containerd runtime, such as windows_ltsc_containerd or windows_sac_containerd .
Describe alternatives you've considered
We could instead drop our support for windows.
Additional context
I'm not sure if we need to change anything in our build scripts / instructions to support the updated node image.
The text was updated successfully, but these errors were encountered:
According to this, since GKE version 1.23, it was no longer possible to either create new clusters that use Docker-based node images or add new node pools with Docker-based node images to an existing cluster. So our instructions and commands to create the Windows node pool was already incorrect since then.
I'm testing #2910 by following this to run the simple-game-server on windows node. But the game server pods keep failing health check. Then I tried to run the simple-game-server on a windows node (with WINDOWS_LTSC image) within a cluster with lower k8s version (1.22), it still failed the health check.
Is your feature request related to a problem? Please describe.
With Kubernetes 1.24, GKE will no longer be supporting node images with the dockershim runtime, which includes
windows_ltsc
(the image currently used in our windows instructions).Describe the solution you'd like
We should switch to a node image with the containerd runtime, such as
windows_ltsc_containerd
orwindows_sac_containerd
.Describe alternatives you've considered
We could instead drop our support for windows.
Additional context
I'm not sure if we need to change anything in our build scripts / instructions to support the updated node image.
The text was updated successfully, but these errors were encountered: