The current node images used in the "Manifest acceptance tests" workflow have a few different issues:
For the images currently in use:
v1.30.0@sha256:047357ac0cfea04663786a612ba1eaba9702bef25227a794b52890dd8bcd692e - valid image, but for kind v0.23
v1.28.9@sha256:dca54bc6a6079dd34699d53d7d4ffa2e853e46a20cd12d619a09207e35300bd0 - valid image, but for kind v0.23
v1.26.6@sha256:f52781bc0d7a19fb6c405c2af83abfeb311f130707a0e219175677e366cc45d1 - SHA actually points to a v1.25 image, and is for kind v0.17
v1.25.11@sha256:577c630ce8e509131eab1aea12c022190978dd2f745aac5eb1fe65c0807eb315 - SHA actually points to a v1.24 image, and is for kind v0.17
v1.23.15@sha256:ef453bb7c79f0e3caba88d2067d4196f427794086a7d0df8df4f019d5e336b61 - SHA actually points to a v1.23.13 image, and is for kind v0.17
v1.27.3@sha256:691e24bd2417609db7e589e1a479b902d2e209892a10ce375fab60a8407c7352 - SHA actually points to a v1.26 image, and is for kind v0.17
The images for Kubernetes versions < 1.30 are easy enough to sort out by using the correct SHAs for the versions and kind version, but the 1.30 image is no available for kind < 0.23 so keeping that would require bumping the version off kind. 1.29 is available for the currently used version of kind (v0.20). Wanted to get feedback on how we'd want to approach that.
In addition the "include" block seems a little bit odd since it means we only run terraform 1.6.1 against a single version of Kubernetes vs the combination of all the possible options (and the comment is wrong at this point 😄).
Potential Terraform Configuration
n/a
References
This came up while implementing #2563
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
The current node images used in the "Manifest acceptance tests" workflow have a few different issues:
For the images currently in use:
The images for Kubernetes versions < 1.30 are easy enough to sort out by using the correct SHAs for the versions and kind version, but the 1.30 image is no available for kind < 0.23 so keeping that would require bumping the version off kind. 1.29 is available for the currently used version of kind (v0.20). Wanted to get feedback on how we'd want to approach that.
In addition the "include" block seems a little bit odd since it means we only run terraform 1.6.1 against a single version of Kubernetes vs the combination of all the possible options (and the comment is wrong at this point 😄).
Potential Terraform Configuration
n/a
References
This came up while implementing #2563
Community Note