Konflux Archived PipelineRuns
Skill551 starsChanged 6 months agoApache-2.0View on GitHub
Accesses archived Konflux PipelineRuns, TaskRuns, and pod logs via KubeArchive. Auto-applies when checking Konflux PipelineRun results, investigating enterprise contract failures, or retrieving logs from completed Konflux CI runs.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api/AGENTS.mdAGENTS.md
- control-plane-operator/AGENTS.mdAGENTS.md
- .cursor/rules/100-go-mistakes.mdcCursor rule
- .cursor/rules/code-formatting.mdcCursor rule
- .cursor/rules/code-review.mdcCursor rule
- .cursor/rules/create-jira-items.mdcCursor rule
- .cursor/rules/debug-aro-hcp-e2e.mdcCursor rule
- .cursor/rules/git-commit-format.mdcCursor rule
- .cursor/rules/restructure-commits.mdcCursor rule
- create-cpo-overrideSkill
- Debug ClusterSkill
- e2e-analyzeSkill
- Effective GoSkill
- feature-developmentSkill
- fix-hypershift-repo-robot-prSkill
- Git Commit FormatSkill
- konflux-buildSkill
- pr-reportSkill
- restructure-commitsSkill
- test-tag-pipelineSkill
- triage-leaked-infraSkill
- update-konflux-tasksSkill
- validate-pr-override-imagesSkill
- Git Commit FormatSkill
- restructure-commitsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 139
KubeArchive
/livezfails: Check that oc is logged in to the correct cluster (api.stone-prd-rh01.pg1f.p1.openshiftapps.com:6443)
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Konflux Archived PipelineRun Access
This skill provides the workflow for accessing Konflux PipelineRuns that have been archived by the kube archiver. PipelineRuns are archived quickly after completion and are typically NOT available via oc get. Use the KubeArchive REST API to retrieve PipelineRun details, TaskRun results, and pod logs.
When to Use This Skill
This skill automatically applies when:
- Checking results of any completed Konflux PipelineRun
- Investigating Konflux enterprise contract check failures
- Retrieving logs from finished Konflux CI builds or tests
- Analyzing trusted task violations in CI
- Looking at Konflux check results on GitHub PRs
- A PipelineRun is not found via
oc getin the Konflux namespace
Architecture
Konflux CI on HyperShift
- Namespace:
crt-redhat-acm-tenant - Cluster:
api.stone-prd-rh01.pg1f.p1.openshiftapps.com:6443 - PipelineRuns are archived quickly by kube archiver and are typically NOT available via
oc get
KubeArchive
Archived PipelineRuns, TaskRuns, pods, and pod logs are accessible through the KubeArchive REST API:
KA_HOST="https://kubearchive-api-server-product-kubearchive.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com"Authentication uses the oc token:
curl -s -H "Authorization: Bearer $(oc whoami -t)" "${KA_HOST}/livez"Accessing Archived Resources
Fetch an Archived PipelineRun
curl -s -H "Authorization: Bearer $(oc whoami -t)" \
"${KA_HOST}/apis/tekton.dev/v1/namespaces/crt-redhat-acm-tenant/pipelineruns/<PIPELINERUN_NAME>"Child TaskRun references are in status.childReferences:
data['status']['childReferences'] # list of {name, kind, apiVersion, pipelineTaskName}Fetch an Archived TaskRun
curl -s -H "Authorization: Bearer $(oc whoami -t)" \
"${KA_HOST}/apis/tekton.dev/v1/namespaces/crt-redhat-acm-tenant/taskruns/<TASKRUN_NAME>"TaskRun results are in status.results.
Find Pods for a TaskRun
curl -s -H "Authorization: Bearer $(oc whoami -t)" \
"${KA_HOST}/api/v1/namespaces/crt-redhat-acm-tenant/pods?labelSelector=tekton.dev/taskRun=<TASKRUN_NAME>"Fetch Pod Logs
List available containers first from the pod spec (spec.initContainers and spec.containers), then fetch logs:
curl -s -H "Authorization: Bearer $(oc whoami -t)" \
"${KA_HOST}/api/v1/namespaces/crt-redhat-acm-tenant/pods/<POD_NAME>/log?container=<CONTAINER_NAME>"Enterprise Contract Violations
Identifying Failing EC Checks from GitHub
HEAD_SHA=$(gh pr view <PR> --repo openshift/hypershift --json headRefOid -q .headRefOid)
# Find failing EC check runs
gh api repos/openshift/hypershift/commits/${HEAD_SHA}/check-runs --paginate \
--jq '.check_runs[] | select(.name | test("enterprise-contract")) | select(.conclusion == "failure") | {name: .name, id: .id}'
# Get PipelineRun names from check output
gh api repos/openshift/hypershift/commits/${HEAD_SHA}/check-runs --paginate \
--jq '.check_runs[] | select(.name | test("enterprise-contract")) | select(.conclusion == "failure") | .output.text'The PipelineRun name appears in an <a href="..."> tag in the output text.
EC Verify Task Pod Containers
The EC verify task pod has these containers with useful output:
step-report-json- Structured JSON with all violations (preferred)step-summary- Human-readable summarystep-detailed-report- Detailed report
EC JSON Report Structure
{
"success": false,
"components": [{
"name": "component-name",
"containerImage": "quay.io/...",
"violations": [{
"msg": "Human-readable message",
"metadata": {
"code": "rule.code.name",
"title": "Rule title",
"description": "Rule description",
"solution": "How to fix"
}
}]
}]
}Group violations by metadata.code and present a summary with counts, rule names, and individual messages.
Common EC Violation Types
tasks.required_untrusted_task_found
A required task is present but not resolved from a trusted version. Fix by updating the task reference in .tekton/ pipeline files.
trusted_task.trusted
A task version is not in the trusted task list. The violation message includes the required SHA to upgrade to. Fix by updating task digests in .tekton/ pipeline files.
Error Handling
oc whoami -tfails: User must log in to the Konflux cluster withoc login- KubeArchive
/livezfails: Check thatocis logged in to the correct cluster (api.stone-prd-rh01.pg1f.p1.openshiftapps.com:6443) - KubeArchive returns 404 for a resource: May not be archived yet; try
oc getdirectly in namespacecrt-redhat-acm-tenant - Pod logs return "no logs found": Logs may have been purged; fall back to TaskRun results for the summary
- No failing EC checks found: Report that all EC checks passed
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

