From 1374b7ca89d069aafc7e55be1ea46ed13ac1196d Mon Sep 17 00:00:00 2001 From: Vincent Shen Date: Fri, 7 Aug 2026 00:30:27 -0700 Subject: [PATCH] Restore the k8scontent publish workflow The k8s GitHub Actions were removed in #13567 as no longer needed, but the Compliance Operator e2e lanes still pull ghcr.io/complianceascode/k8scontent:latest as their content image. The tag has been frozen at the 2025-06-13 build since the removal, so CO CI has been testing against year-old content. Among other drift, that old content predates the kubelet rule filepath move to /tmp/runtime/openscap-kubeletconfig (82fc125c0e), which blocks the operator-side half of that change from passing e2e. Restore the push-triggered publish workflow only (k8s-content.yaml); the removed PR-test variants stay removed. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/k8s-content.yaml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .github/workflows/k8s-content.yaml diff --git a/.github/workflows/k8s-content.yaml b/.github/workflows/k8s-content.yaml new file mode 100644 index 00000000000..563637a11af --- /dev/null +++ b/.github/workflows/k8s-content.yaml @@ -0,0 +1,23 @@ +--- +name: Kubernetes content + +on: + push: + branches: ['master'] + +jobs: + container-main: + permissions: + contents: read + id-token: write + packages: write + uses: metal-toolbox/container-push/.github/workflows/container-push.yml@main + with: + name: k8scontent + tag: ${GITHUB_SHA} + latest: true + registry_org: complianceascode + dockerfile_path: ./Dockerfiles/ocp4_content + licenses: BSD + vendor: ComplianceAsCode authors + platforms: 'linux/amd64,linux/ppc64le,linux/s390x,linux/arm64'