Repository navigation
ci: run the CNTi essential tests nightly and show the result as a badge - #669
Conversation
3abbb1e to
6065b39
Compare
6065b39 to
8f718a2
Compare
8f718a2 to
c6dd3cb
Compare
c6dd3cb to
e1e3ebe
Compare
877ae38 to
433c780
Compare
433c780 to
7c94f39
Compare
7c94f39 to
2a0323d
Compare
2a0323d to
ee203ce
Compare
A workflow installs the chart with its defaults on a kind cluster of a control plane and two workers, runs the CNTi Test Suite's essential tests against it with lfn-cnti/testsuite-action, and publishes the result as a badge in the README. - essential: nightly and by hand on main; the only job that publishes the badge, to the orphan branch badges, and the only one with a write token. - essential-pr: the same steps read-only on pull requests that change the job, its configuration or the chart, and on manual runs of other branches. - Both run only in edgecomllc/eupf, so forks with scheduled workflows on don't run them. Suite v2.3.0, action v1.2.0, pinned by commit. - .github/cnti/: the suite configuration (the chart's defaults, nothing else) and the kind config, whose kubelets allow net.ipv4.ip_forward and whose nodes have the host's bpffs at /sys/fs/bpf, as the chart README asks. Signed-off-by: Martin Matyas <[email protected]> Co-Authored-By: Claude Opus 5.5 <[email protected]>
ee203ce to
0c3be81
Compare
|
@martin-mat It seems we’re ready to merge this pull request, isn’t it? |
|
@pirog-spb yes, it's ready, thanks for re-approving. One thing after merging: the badge branch badges is created by the first run on main, so the README badge shows nothing until then. Running "CNTi essential" once by hand from the Actions tab (on main) publishes it right away; otherwise the nightly does at 03:37 UTC. |
…ge (#669) Signed-off-by: Martin Matyas <[email protected]> Co-authored-by: Claude Opus 5.5 <[email protected]> (cherry picked from commit 4433619) Signed-off-by: pirog-spb <[email protected]>
eUPF's badge job went live on main on 31 Oct (edgecomllc/eupf#669). It runs nightly with the action's defaults, its own kind config and no steps of its own before the action, so its entry needs no prepare or environment. Signed-off-by: Martin Matyas <[email protected]> Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
@pirog-spb heads-up: the first nightly on main failed, and the cause is the chart, not the tests: run 41298996824.
Anyone installing the chart from main with its defaults hits the same error, so the root fix is to have the chart's The badge still shows 16/19 because a failed install publishes no new score, so it stays at the last good result until a nightly installs again. |
eUPF's badge job went live on main on 31 Oct (edgecomllc/eupf#669). It runs nightly with the action's defaults, its own kind config and no steps of its own before the action, so its entry needs no prepare or environment. Signed-off-by: Martin Matyas <[email protected]> Co-Authored-By: Claude Opus 5.5 <[email protected]>
Adds the nightly CNTi essential-tests check and badge proposed in #668. A workflow installs the chart with its defaults on a kind cluster of a control plane and two workers, runs the CNTi Test Suite's essential tests with lfn-cnti/testsuite-action, and shows the result as a badge in the README.
.github/workflows/cnti.yml:essentialruns nightly and by hand onmain. It's the only job that publishes the badge, to the orphan branchbadges, and the only one with a write token.essential-prruns the same steps read-only on pull requests that change the job, its configuration or the chart, and on manual runs of other branches.edgecomllc/eupf, so forks with scheduled workflows enabled don't run them..github/cnti/cnti-testsuite.yaml: the suite configuration. The chart is installed with its defaults. The only settings are the released image tags the rolling update, downgrade and rollback tests move to (0.7.0 and 0.6.4)..github/cnti/kind.yaml: three nodes, withnet.ipv4.ip_forwardallowed on every kubelet, as the chart README asks.README.md: the badge in the existing badge row.Tested on martin-mat/eupf, on top of the current
main, with the repository guard pointed at the fork:mainessentialwith a write token: 14 of 19, 4 min, badge publishedmainwith #666essential-pr, read-only: 15 of 19, passes, nothing published.github/cnti/essential-pr, read-only: 14 of 19, nothing publishedBest merged after #666, so the first nightly is green. The issue explains the four tests that still don't pass.
Closes #668.
🤖 Generated with Claude Code