feat: (IAC-901) Add K8s 1.25 support and Support Aliased Versions #161
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Since the SAS Viya Platform will be supporting K8s 1.23, 1.24, and 1.25 in March as part of the 2023.03 cadence, the kubectl version is being changed to 1.24.10 so that it's within the +/- 1 range of the supported versions.
We've also now added support for using aliased kubernetes versions.
This is only applicable in the "version based" scenario (omitting
kubernetes_channel
or setting it to "UNSPECIFIED"), Google supports the use of aliased versions when creating your kubernetes cluster. The required format for using aliased versions in your tfvars forkubernetes_version
looks like:For example you could set:
And Google will choose the "highest valid patch+gke.N patch release in the 1.24 minor version" they currently have available.
Setting the full version like before is still supported. (e.g. 1.24.9-gke.3200)
The Kubernetes Versions documentation has been updated to describe this usage
Tests
Ran through the following scenarios, the internal ticket has more details.