swaphb/kubernetes-security-baseline-lab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

support kube-bench artifacts on Gitea Actions
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Failing after 7m5s
Details

Browse Source
This commit is contained in:
swaphb
2026-08-11 19:07:21 -04:00
parent 5ddb0f2fef
commit c272dd4581
2 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/kube-bench-scan.yml
+3 -1
View File
@@ -119,7 +119,9 @@ jobs:
- name: Upload kube-bench report - name: Upload kube-bench report
if: always() if: always()
uses: actions/upload-artifact@v4 # Upstream v4 rejects Gitea because it identifies as GHES.
# This compatible fork retains the v4 interface on both forges.
uses: christopherHX/gitea-upload-artifact@v4
with: with:
name: kube-bench-k3s-cis-1.7 name: kube-bench-k3s-cis-1.7
path: artifacts/kube-bench-k3s-cis-1.7.json path: artifacts/kube-bench-k3s-cis-1.7.json
ci/README.md
+5
View File
@@ -48,6 +48,11 @@ access because the workflow creates a k3d cluster and runs the kube-bench Job.
Register a dedicated runner for this repository rather than sharing a runner Register a dedicated runner for this repository rather than sharing a runner
with unrelated repositories. with unrelated repositories.
The report upload uses the Gitea-compatible `gitea-upload-artifact` v4 fork.
The upstream `actions/upload-artifact` v4 action identifies Gitea as GitHub
Enterprise Server and exits before uploading. The compatible fork retains the
same workflow interface for GitHub Actions and Gitea Actions.
Example Docker runner setup, with the registration token supplied separately: Example Docker runner setup, with the registration token supplied separately:
```bash ```bash