What you expected to happen:
The Agones SDK Docker image should recognize and be compatible with the actual OS version of the node, whether it is Windows 2022 or Windows 2019. The os.version field should be present in the Docker image manifest to ensure the correct image is pulled according to the node's OS.
How to reproduce it (as minimally and precisely as possible):
Attempt to deploy the Agones SDK Docker image on a Windows 2022 node.
Anything else we need to know?:
This issue is not limited to the Agones SDK image; it is likely to affect other Agones Docker images as well.
Environment:
Agones version: 1.41
Kubernetes version (use kubectl version): 1.29
Cloud provider or hardware configuration: aks windows2022 node
What happened: The Agones SDK image cannot be used on Windows 2022 nodes. This issue occurs consistently across all versions starting from 1.40. The root cause appears to be the absence of the os.version field in the Docker image manifest. Consequently, the image is always pulled as if it were for Windows 2019, regardless of whether the actual node OS is Windows 2022 or Windows 2019. https://console.cloud.google.com/artifacts/docker/agones-images/us/release/agones-sdk/sha256:3684e3e93891c8faf6a6e69aad2f86986011ee0596d26c3b84499e500b6bbade;tab=manifest
What you expected to happen: The Agones SDK Docker image should recognize and be compatible with the actual OS version of the node, whether it is Windows 2022 or Windows 2019. The os.version field should be present in the Docker image manifest to ensure the correct image is pulled according to the node's OS.
How to reproduce it (as minimally and precisely as possible): Attempt to deploy the Agones SDK Docker image on a Windows 2022 node.
Anything else we need to know?: This issue is not limited to the Agones SDK image; it is likely to affect other Agones Docker images as well.
Environment:
kubectl version): 1.29