Skip to content

docs: add CK8s image-builder release process#21

Open
vomba wants to merge 1 commit into
ck8s/mainfrom
docs/ck8s-release-md
Open

docs: add CK8s image-builder release process#21
vomba wants to merge 1 commit into
ck8s/mainfrom
docs/ck8s-release-md

Conversation

@vomba

@vomba vomba commented Jul 15, 2026

Copy link
Copy Markdown
  • Add CK8S_RELEASE.md documenting how we maintain the image-builder fork
  • Defines the ck8s/main branch model: main stays a conflict-free upstream mirror, all CK8s changes live on ck8s/main
  • Documents release branching, staging, tagging, and artifact publishing

Context

This PR follows bootstrapping ck8s/main from the current CK8s patch set (7 commits on top of upstream v0.1.55).

Document the ck8s/main branch model, upstream sync workflow, and
release staging process aligned with compliantkubernetes-kubespray.
@vomba vomba mentioned this pull request Jul 15, 2026

@viktor-f viktor-f left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice document, I think the process makes sense and the examples are very good.

Comment thread CK8S_RELEASE.md

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have this generic process for managing forks. Should we perhaps link this specific process in the generic document? So that if someone looks at the generic process they can then see that there is a more specific process for this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants