scripts: temporarily disable kubernetes deploy/upgrade steps#2925
Merged
Conversation
ideaship
requested changes
Jul 8, 2026
ideaship
left a comment
ideaship
left a comment
Contributor
There was a problem hiding this comment.
This PR lacks information on why we are doing this. It's rather unusual to disable tests for an active feature. If we are reducing test coverage, we should a) state that this feature is removed permanently, or b) describe when it can/should be enabled again. Usually, features are re-enabled when they pass a test again, but after having testing itself disabled, it's unclear how the feature could ever come back.
github-project-automation
Bot
moved this from Ready for review
to In review
in Human Board
Remove the kubernetes deploy and upgrade stage invocations from deploy-services.sh and upgrade-services.sh while disabled. The k3s deployment is currently a tech preview and does not work because the required Kubernetes version jump is too large to upgrade through directly. This needs to be fixed before k3s can be re-enabled. Since we do not use k3s ourselves, it is removed for now to keep the testbed stable, and will be added back once the upgrade path has been fixed. Assisted-by: Claude:claude-sonnet-5 Signed-off-by: Christian Berendt <berendt@osism.tech>
berendt
force-pushed
the
temp-disable-k8s-deploy
branch
from
cb88c78 to
75e056d
Compare
ideaship
approved these changes
Jul 8, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
scripts/deploy-services.shscripts/upgrade-services.shThe k3s deployment is currently a tech preview and does not work: the
upgrade playbook jumps directly from Kubernetes 1.32 to 1.36 instead of
upgrading one minor version at a time, which is unsupported per the
Kubernetes version skew policy.
Since we do not use k3s ourselves, the stage is disabled for now to keep
the testbed stable, and will be re-enabled once the upgrade path is fixed.
Tracked upstream in osism/osism-kubernetes#313.
Test plan
deploy-services.shand confirm it skips the kubernetes stageupgrade-services.shand confirm it skips the kubernetes stage