Repository navigation
Tags
Tags
kubeadm: reconcile patch-only control-plane changes (#403) Compare live control-plane manifests with kubeadm dry-run output using the selected generation's native patches. Regenerate affected components and wait for healthy replacement pods before reporting success. Skip shared configuration upload when it already matches. Fixes #402.
release: prepare 2026.11.0-beta.1 operator guidance (#395) Link the external-worker enrollment and lifecycle procedure, explain the direct-etcd upgrade requirements, and retain known host maintenance limitations for the November beta. Keep operational guidance alongside the source that the release pipeline qualifies and publishes. Release-Note: skip
release: prepare 2026.10.4 upgrade guidance Explain that the CoreDNS ownership fix runs in the KatlOS node agent and requires a host upgrade before retrying Kubernetes upgrades. Link the supported host and Kubernetes procedures, and carry forward the known Ceph maintenance and vendor LTS power-button limitations. Release-Note: skip
runtime: build pinned containerd and crun RPMs Build containerd 2.3.7 with its matching shim and crun 1.30.1 from verified upstream sources, package them against Fedora libraries, and install exact RPM versions in KatlOS. Runtime security updates can ship independently of Fedora package availability while retaining systemd cgroups, PIE hardening, and immutable node upgrades. Add Renovate inputs for versions, source integrity, and the Go toolchain. Preserve generation-owned legacy kubeadm inputs before traversing ancestors so existing nodes can prepare the upgrade without losing their configuration. Document the security update and supported maintenance path for 2026.10.3. Release-Note: Update containerd to 2.3.7 and crun to 1.30.1.
release: qualify production lifecycles before automatic promotion (#373) Qualify both VM-test flavours and the final production bundle before automatic release promotion. Exercise production installation, reboot, upgrade from the previous stable release, and rollback through SSH and the shipped CLI, then publish the same verified artifacts. Release-Note: skip
docs: keep release guidance links valid after publication (#355) Keep the unpublished candidate link in the documentation index rather than the release body, where a relative Markdown path would resolve against the GitHub Releases page. Preserve the archive's reachability from the documentation landing page. Release-Note: skip
ci: qualify staged release artifacts before publication (#352) Pause tag publication after the assembled bundle is attested and uploaded, using the protected release environment. Both extension and GitHub publication wait for approval of the same run's artifacts, so a separately rebuilt manual candidate cannot stand in for the shipped bytes. Retain extension publication inputs for the same 30-day approval window and document artifact qualification and approval evidence. Release-Note: skip
apply: reconcile Kubernetes after partial configuration failure (#339) Reconcile configured Kubernetes components when host files already match, so an unchanged retry can finish a failed rollout without creating another generation. Report partial results and retain the component failure and recovery guidance. Require health checks before completing unchanged component operations. Use existing kubelet mutation records to recover incomplete changes and refresh removed settings; tolerate defaulted shared configuration so healthy repeats avoid uploads and restarts. Cover the public failure, retry, repeat, and reboot journey, and document recovery in the 2026.9.1 release notes.
docs: mark 2026.9.0 as the first stable release (#337) Describe the maintainer's home-lab experience and commitment to fixing issues in future releases. Align operator documentation with the stable designation while retaining compatibility, trust, and recovery limits. Release-Note: skip
agent: recover interrupted applies and preserve live boot choices (#314) Recover configuration renders interrupted before mutation by removing only unselected candidates and completing their operations as retryable failures. Mark rolled-back candidates abandoned before releasing their locks so the operation record and generation status agree. Make live promotion replace stale EFI one-shot choices with the promoted generation, including firmware compensation on write failure. Add beta.18 upgrade guidance to generated release notes. Release-Note: Fix interrupted applies and live boot selection
PreviousNext