Restore the k8scontent publish workflow - #14968
Draft
Vincent056 wants to merge 1 commit into
Draft
Conversation
Vincent056
requested review from
Mab879,
ggbecker,
jan-cerny,
marcusburghardt and
vojtapolasek
as code owners
August 7, 2026 07:30
|
@Vincent056: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Vincent056
marked this pull request as draft
August 7, 2026 15:02
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
Mab879
requested changes
Aug 7, 2026
Mab879
left a comment
Mab879
left a comment
Member
There was a problem hiding this comment.
Please fix the YAML lint findings.
The k8s GitHub Actions were removed in ComplianceAsCode#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 (82fc125), 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) <noreply@anthropic.com>
Vincent056
force-pushed
the
restore-k8scontent-publish
branch
from
August 7, 2026 19:42
afc63b6 to
1374b7c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Restore the push-triggered
k8s-content.yamlworkflow that publishesghcr.io/complianceascode/k8scontent(:latest+ per-commit SHA tags). Restored verbatim from before the removal; themetal-toolbox/container-pushreusable workflow it depends on still exists. The removed PR-test variants stay removed.Rationale:
The k8s GitHub Actions were removed in #13567 as "no longer needed", but the Compliance Operator e2e lanes still pull
ghcr.io/complianceascode/k8scontent:latestas their default content image (DEFAULT_CONTENT_IMAGEin the compliance-operator Makefile). The tag has been frozen at the 2025-06-13 build ever since - CO CI has been testing against year-old content for 14 months.Concrete breakage this masked: 82fc125 (June 2026) moved the kubelet rule filepath to
/tmp/runtime/openscap-kubeletconfig, but the frozen image still reads/var/run/compliance-operator/kubeletconfig/.... The operator-side half of that change (ComplianceAsCode/compliance-operator#1255) cannot pass e2e against the stale image, while the current operator only passes because the image is stale.Sequencing note for reviewers: once
:latestrefreshes, the compliance-operator master serial lane's kubelet tests will fail until compliance-operator#1255 (which delivers the new path) merges - that PR is approved and ready, so the window can be kept short.🤖 Generated with Claude Code