Repository navigation
Conversation
feat: talos-image.yaml ledger, machine class installImage, CI pipeline
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
chore: Talos upgrade to v1.12.6
* chore: Talos upgrade to v1.13.5 (k8s v1.36.2) * chore: Talos upgrade to v1.13.5 (k8s v1.36.2) --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…10) The talos-images upgrade workflow rewrites omni/talos-image.yaml and omni/machine-classes/*.yaml, but never omni/cluster-templates/talos.yaml. The template has therefore drifted: it pinned Talos v1.12.5 while the machine classes install v1.12.6, and it is the file Omni actually applies. Move it to v1.13.5 to match PR #9. kubernetes.version is left at v1.32.3 on purpose and annotated: it is human-owned, and Talos 1.13.x still supports it.
generate-manifests.sh now takes ARGO_MODE=in-cluster|hub. Default in-cluster keeps today's behaviour (Argo + root App-of-Apps bootstrapped inside the cluster). ARGO_MODE=hub emits only the Cilium inline manifest and omits the two argocd blocks, so the cluster boots with no in-cluster Argo and is managed by a central hub Argo (on the Omni VM k8s) as a spoke. Script-only: the committed inline-manifests.yaml is unchanged until someone regenerates with a chosen mode.
…tion In ARGO_MODE=hub, emit the argocd-manager ServiceAccount, cluster-admin binding, and a named (non-expiring) token Secret as inline manifests, so a hub-mode spoke is registration-ready at first boot. The one manual step (read token → sops → commit) is documented in the hub registration runbook; the inline comment points there rather than restating it.
Contributor
Author
|
Superseded by the generate-manifests.sh multi-cluster rewrite (yq-based inject(), oci-lab/unraid-lab routing). ARGO_MODE toggle needs to be re-implemented against the new script rather than merged — re-scoping as new work. Branch left in place for reference. |
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.
What
omni/scripts/generate-manifests.shgains anARGO_MODEvariable:in-cluster(default)hubCilium is always in-cluster — it is the CNI and cannot be remote.
Why
The Argo topology is a decision, not a fixed part of the design. For this free-tier lab the target is a single central hub on the Omni VM's k8s (spokes run zero Argo, giving the scarce 2 OCPU / 12 GB back to workloads). This makes that switch a first-class IaC toggle rather than a manual edit of the inline manifests.
Scope / safety
Script-only. The committed
omni/patches/inline-manifests.yamlis unchanged — it regenerates only when someone runs the script with a chosen mode. Invalid modes fail fast.bash -nclean.Not in this PR (the hub side)
hubmode removes in-cluster Argo but does not yet deploy the hub. The companion work: ak8s/argocd/base onomni-on-unraid, and spoke registration (Argo cluster secret → each cluster's API over Tailscale). Tracked separately.