feat: add support for k8s 1.28 #1546
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
j-zimnowoda
approved these changes
Mar 8, 2024
src/supportedK8sVersions.json
Outdated
| @@ -1 +1 @@ | |||
| { "supportedK8sVersions": ["1.25", "1.26", "1.27"] } | |||
| { "supportedK8sVersions": ["1.26", "1.27", "1.28"] } | |||
There was a problem hiding this comment.
We can add 1.28 without deprecating 1.25 yet.
Then we can add support already in release v2.9 instead of waiting for v3.0.
There was a problem hiding this comment.
Updated supportedK8sVersions and package.json without deprecating 1.25 for v2.9.
|
Tested full deployment: https://github.com/redkubes/otomi-core/actions/runs/8200774105/job/22428196117 All good |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implements:
https://app.zenhub.com/workspaces/dev-5e7e84dddc966f05a627a19b/issues/gh/redkubes/otomi-core/1445
Test:
Tested the installation on a new cluster with the
full.yamltest case scenario.