jlab-cluster/helm-charts
3
0 Fork 0
Code Issues 15 Pull Requests 3 Actions Packages Wiki Activity

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

Browse Source 
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.
This commit is contained in:
jklein committed 2026-09-17 00:39:05 +02:00
1 parent eaaad24b98
commit ad573406a5
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
freesailarr/Chart.yaml
+1 -1
View File
@@ -8,7 +8,7 @@ description: A Helm chart to deploy a Wireguard-tunneled media automation stack
type: application
version: 3.0.6+up1.0.0
version: 3.0.5+up1.0.0
# The chart's own version marker, freely chosen and tied to no upstream. The
# stack bundles nine independently versioned projects, so there is no single
# "app version" to track here.