jlab-cluster/helm-charts
3
0 Fork 0
Code Issues 15 Pull Requests 3 Actions Packages Wiki Activity
Files
ad573406a512f54739fa87467ff8c2340fae4c68
helm-charts/freesailarr
T
History
jklein ad573406a5
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
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.
2026-09-17 00:39:05 +02:00
..
templates
freesailarr: no exponential notation in computed limits (3.0.2+up1.0.0)
2026-08-29 01:08:07 +02:00
.helmignore
Add freesailarr chart: gluetun-tunneled media automation stack
2026-08-24 13:41:46 +02:00
Chart.yaml
probe: cyberchef only, to separate resource contention from the rest
2026-09-17 00:39:05 +02:00
values.schema.json
freesailarr: shared domain with sub-paths, qBittorrent save path (3.0.0+up1.0.0)
2026-08-25 20:55:43 +02:00
values.yaml
Update docker.io/linuxserver/bazarr Docker tag to v1.6.0
2026-08-30 01:20:22 +00:00