docs(clusters): document k3s-rabbit/oc-ampere e2e coverage and fix stale oc-ampere description - #1798
Merged
Merged
Conversation
…ale oc-ampere description Companion to the e2e workflow PRs adding validate-k3s-rabbit.yml and validate-oc-ampere.yml: - clusters/CLAUDE.md: add both workflows to the CI table, fix the stale "Teleport agent only" oc-ampere cluster-table description (it has 4 real apps), fix the same staleness in the Slack-alerting "not extended" rationale, and document the EXCLUDED_APPS-first fail-closed per-app loop shared across all four cluster e2e workflows plus why no concurrency guard is needed (both self-hosted runners are confirmed distinct physical machines). - Both new clusters' root kustomization.yaml gain the same "this resources: list is parsed by ..." header comment kubenuc/ k8s-vms-daniele already carry, so a new top-level resource doesn't silently lose e2e coverage. oc-ampere's also documents why flux-instance.yaml must stay skip-listed there specifically. - clusters/k3s-rabbit/CLAUDE.md: document that its e2e workflow deploys zero apps by design (3/3 real apps excluded) and what the run still proves. - clusters/oc-ampere/CLAUDE.md: new file (didn't exist before). Documents the ARM64-production/x86_64-CI mismatch, the real app inventory, the no-1Password gap, and the flux-operator pre-FluxInstance safety finding from the e2e PR. Signed-off-by: Daniele De Lorenzi <2905124+dark-vex@users.noreply.github.com>
dark-vex
added a commit
that referenced
this pull request
Aug 7, 2026
docs(clusters): document k3s-rabbit/oc-ampere e2e coverage and fix stale oc-ampere description
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
1 participant
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.
Summary
Companion to #1796 (
validate-k3s-rabbit.yml) and #1797 (validate-oc-ampere.yml).clusters/CLAUDE.md: adds both new workflows to the CI table, fixes the stale "Teleport agent only"oc-amperecluster-table description (it has 4 real apps) and the same staleness in the Slack-alerting "not extended" rationale, and documents the sharedEXCLUDED_APPS-first fail-closed per-app loop plus why noconcurrency:guard is needed across the 4 cluster e2e workflows — confirmed both self-hosted runners (gen8-runner/Lugano,psp-runner/BGY) are distinct physical machines that each process one job at a time, so GitHub's own scheduling already prevents same-machine collisions.kustomization.yamlgain the same "thisresources:list is parsed by ..." header commentkubenuc/k8s-vms-danielealready carry.clusters/k3s-rabbit/CLAUDE.md: documents the "zero apps deploy by design" framing for its e2e workflow.clusters/oc-ampere/CLAUDE.md: new file (didn't exist before) — documents the ARM64-production/x86_64-CI mismatch, the real 4-app inventory, the no-1Password gap, and theflux-operatorpre-FluxInstancesafety finding from ci(validate-oc-ampere): add e2e cluster validation workflow #1797.Test plan
pre-commit(check-yaml,trailing-whitespace,gitleaks) passes on all touched fileskustomization.yamlfiles still parse (verified via the Mechanism 1 parser tests in ci(validate-k3s-rabbit): add e2e cluster validation workflow #1796/ci(validate-oc-ampere): add e2e cluster validation workflow #1797)🤖 Generated with Claude Code