chore(kube-ovn): bump chart 1.15.6 -> 1.15.9 - #194
Open
gurinderu wants to merge 1 commit into
Open
Conversation
ValeryAntopol
approved these changes
Aug 6, 2026
gurinderu
changed the title
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
2 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.
Max patch within the 1.15 line, taken before the minor jump to 1.16.2 later in the upgrade ladder.
Why the patch bump is its own step: by the ordering invariant the kube-ovn minor goes last, so it does not mix with the kernel and k8s changes. The patch within the line is safe and goes first.
Note: earlier planning notes referenced 1.15.20 — that version does not exist. In the kube-ovn-v2 chart repo the 1.15 line ends at 1.15.9, followed directly by 1.16.0…1.16.2.
Rollout: merging to main deploys to stage only — overlays/stage tracks branch main, while testnet and mainnet are pinned to git tags and are unaffected.
Cluster impact: ovs-ovn rollout; VMs are not restarted, brief connectivity blip.
Post-merge check: kube-ovn v1.15.9 in the kube-system daemonset/deployment; VMIs alive; canary pair reachable.