probe: cyberchef only, to separate resource contention from the rest

The two-leg run on Gitea left the cyberchef pod Pending with no node and no scheduling event, while its k3s node logged a Starting event 17s after the deployment was created - the node restarted under it. Two k3s clusters share one runner container there (6 CPU / 12Gi per #227), where on GitHub two legs are two VMs. A single leg, repeated, tells contention apart from a real fault.
probe: both charts (GitHub host path, with the race fixed)
2026-09-17 00:39:05 +02:00 · 2026-09-17 00:39:01 +02:00
1 changed files with 1 additions and 1 deletions
@@ -5,7 +5,7 @@ icon: https://raw.githubusercontent.com/gchq/CyberChef/master/src/web/static/ima
 type: application
-version: 9.0.1+up11.4.0
+version: 9.0.2+up11.4.0
 appVersion: "11.4.0"
 maintainers:
Author	SHA1	Message	Date
jklein	ad573406a5	probe: cyberchef only, to separate resource contention from the rest Validate Helm Charts / Detect changed charts (pull_request) Successful in 3s Details Validate Helm Charts / Resource quantities (pull_request) Successful in 7s Details Validate Helm Charts / Build ${{ fromJSON(needs.detect-changed-charts.outputs.charts) }} (pull_request) Successful in 4s Details Validate Helm Charts / Trivy config ${{ fromJSON(needs.detect-changed-charts.outputs.scan-charts) }} (pull_request) Successful in 10s Details Validate Helm Charts / Install-test ${{ fromJSON(needs.detect-changed-charts.outputs.install-charts) }} (pull_request) Failing after 5m30s Details The two-leg run on Gitea left the cyberchef pod Pending with no node and no scheduling event, while its k3s node logged a Starting event 17s after the deployment was created - the node restarted under it. Two k3s clusters share one runner container there (6 CPU / 12Gi per #227), where on GitHub two legs are two VMs. A single leg, repeated, tells contention apart from a real fault.	2026-09-17 00:39:05 +02:00
jklein	eaaad24b98	probe: both charts (GitHub host path, with the race fixed)	2026-09-17 00:39:01 +02:00