Add patch version upgrade section to orka-upgrades doc#139
Draft
Add patch version upgrade section to orka-upgrades doc#139
Conversation
Documents that node additions require the cluster to be on the latest patch version for its major.minor branch, and that patch upgrades are zero-downtime. Previously this was undocumented and surfaced only as a support escalation when node add workflows failed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Patch is a sub-type of an Orka software release, not a peer of major/minor or K8s upgrades. Folded the single-sentence prep note into the intro. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
clarify verbiage
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
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
Context
Node add failures on clusters running older patch versions (e.g., 3.5.0 vs. 3.5.2) have come up in support multiple times. This documentation adds context for customers.
Test plan
<Note>callout about node additions is visible and accurate🤖 Generated with Claude Code