Simplify k0s Release Process Using Git Patches #2172
Draft
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.
What this PR does / why we need it:
This PR proposes replacing long-lived version branches (e.g.,
k0s-1-28
,k0s-1-29
) with a Git patch-based workflow. Instead of maintaining separate branches per minor version, we’ll keep all development onmain
and apply version-specific patches at build time via CI.Benefits
How It Works
patches/k0s-<version>/
main
, applies the relevant patches, and builds/releases from theregit diff
from a branch. For example:git diff > 001-k0s-metadata.patch
Impact
This approach keeps the build deterministic and isolated per version, with minimal changes to runtime behavior or release artifacts.
Which issue(s) this PR fixes:
SC-123682
Does this PR require a test?
Yes
Does this PR require a release note?
Does this PR require documentation?
NONE