feat(helm): release check on most-supported Kubernetes version #848
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
…hub#848) Since Kubernetes 1.22, there was never a big need to actually upgrade REANA source code to make it work on new Kubernetes releases. (This is thanks to the fact that REANA uses pretty stable Kubernetes API internally.) This commit therefore releases the upper boundary check on the supported Kubernetes versions in order to be more welcoming to future Kubernetes upgrades, alleviating the need to manually bump the supported version number.
tiborsimko
force-pushed
the
k8s-release-upper-bound
branch
from
4e1c8e4 to
1a98b0a
Compare
tiborsimko
changed the title
tiborsimko
added a commit
to tiborsimko/reana
that referenced
this pull request
Dec 18, 2024
chore(maint-0.9): release 0.9.4 (reanahub#768) fix(reana-dev): correctly handle missing changelog of components (reanahub#858) fix(helm): allow interactive-session-cleanup job to access RWC (reanahub#853) feat(helm): release check on most-supported Kubernetes version (reanahub#848) docs(helm): clarify secrets-related warning in README (reanahub#847) feat(helm): allow only reana-server to connect to reana-cache (reanahub#847) feat(helm): support password-protected rabbitmq (reanahub#847) feat(helm): support password-protected redis (reanahub#847) feat(scripts): upgrade to Jupyter SciPy 7.2.2 notebook (reanahub#846)
tiborsimko
added a commit
to tiborsimko/reana
that referenced
this pull request
Dec 18, 2024
chore(maint-0.9): release 0.9.4 (reanahub#768) fix(reana-dev): correctly handle missing changelog of components (reanahub#858) fix(helm): allow interactive-session-cleanup job to access RWC (reanahub#853) feat(helm): release check on most-supported Kubernetes version (reanahub#848) docs(helm): clarify secrets-related warning in README (reanahub#847) feat(helm): allow only reana-server to connect to reana-cache (reanahub#847) feat(helm): support password-protected rabbitmq (reanahub#847) feat(helm): support password-protected redis (reanahub#847) feat(scripts): upgrade to Jupyter SciPy 7.2.2 notebook (reanahub#846)
tiborsimko
added a commit
to tiborsimko/reana
that referenced
this pull request
Dec 18, 2024
chore(maint-0.9): release 0.9.4 (reanahub#768) fix(reana-dev): correctly handle missing changelog of components (reanahub#858) fix(helm): allow interactive-session-cleanup job to access RWC (reanahub#853) feat(helm): release check on most-supported Kubernetes version (reanahub#848) docs(helm): clarify secrets-related warning in README (reanahub#847) feat(helm): allow only reana-server to connect to reana-cache (reanahub#847) feat(helm): support password-protected rabbitmq (reanahub#847) feat(helm): support password-protected redis (reanahub#847) feat(scripts): upgrade to Jupyter SciPy 7.2.2 notebook (reanahub#846)
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.
Since Kubernetes 1.22, there was never a big need to actually upgrade REANA source code to make it work on new Kubernetes releases. (This is thanks to the fact that REANA uses pretty stable Kubernetes API internally.) This commit therefore releases the upper boundary check on the supported Kubernetes versions in order to be more welcoming to future Kubernetes upgrades, alleviating the need to manually bump the supported version number.