Repository navigation
Conversation
…ast release
- vm-bootstrap: Argo CD syncs every layer (MetalLB, the gateway and edge
proxy, cert-manager with the internal CA, Longhorn, Pi-hole, the VPN, a
web app) from the rendered branch, which the VM serves itself over git's
HTTP protocol; passes only when every Application is Synced and Healthy,
the app answers through the gateway, and Longhorn's first sync went
through by itself. The three bootstrap bugs found on real hardware
(AppProject race, gateway health, the sync operation's options) are the
kind it catches.
- vm-upgrade: the previous release's render applied for real, then the
current one over it (server-side dry run, CRDs for real): catches fields
that can't change on existing objects and dropped CRD versions. Checked
by sabotage: a changed Deployment selector is rejected ("field is
immutable").
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
k3s imports every preloaded image (29 here) before the kubelet starts, which took over 5 minutes on CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Argo CD lists refs with go-git, which doesn't speak git's plain HTTP
protocol ("failed to list refs: unexpected EOF"). A small bridge to git
http-backend serves the smart one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… render vm-bootstrap listed its 13 apps by hand, duplicating the render: a core app added later would have been missing from its preloaded images. Groups may now leave apps out, and get every app in their render (and are rerun for any change to it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The render's directories are symlinks into the Nix store; committed as
such, Argo CD refuses the repository ("out-of-bounds symlinks").
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Two VM tests from the readiness checklist.
vm-bootstrap: a fresh cluster bootstraps by itselfArgo CD syncs every layer from the rendered branch, which the VM serves itself over git's HTTP protocol. That's no internet, the internal CA, and digests stripped for the preloaded images. The layers are MetalLB, Traefik with the edge proxy, cert-manager, Longhorn, Pi-hole, the VPN and a web app.
It passes only when:
The three bootstrap bugs found on real hardware are what it targets:
CreateNamespaceandretry.Its 28 images reuse pins other groups already have, and
nix run .#updatekeeps thevm-bootstrapgroup current. It needs an 8 GB VM, so it was run only in CI.vm-upgrade: upgrading from the previous releaseThe previous release's render (v1.24.2, pinned by hash) is applied to a cluster for real. Then the current render is applied over it: CRDs for real, everything else as a server-side dry run, the way Argo CD would. That catches what only breaks on upgrade: fields that can't change on existing objects, and CRD versions still stored but no longer served.
Run locally: it passes. A sabotage run, with a changed Deployment selector, fails as it should:
Deployment "pihole" … spec.selector … field is immutable, 1 of 200 objects rejected. CONTRIBUTING gets a "Releasing" step to bump the pin.🤖 Generated with Claude Code