Konflux Archived PipelineRuns

Retrieves archived Konflux PipelineRuns, TaskRuns, and pod logs via the KubeArchive REST API.

538|560|Updated Jan 18, 2021
One-click install
npx skills add https://github.com/openshift/hypershift --skill konflux-archived-pipelineruns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Konflux Archived PipelineRuns
Source: https://github.com/openshift/hypershift/tree/main/.claude/skills/konflux-ec-violations
Command: npx skills add https://github.com/openshift/hypershift --skill konflux-archived-pipelineruns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Konflux PipelineRuns are archived shortly after completion and disappear from oc get, making it hard to inspect CI results, enterprise contract failures, or build logs. This Skill provides the workflow to query the KubeArchive REST API and recover those archived resources.

Core Features & Use Cases

  • Archived Resource Access: Fetch PipelineRuns, TaskRuns, pods, and container logs from KubeArchive using your oc token.
  • Enterprise Contract Triage: Identify failing EC check runs on GitHub PRs, extract the PipelineRun name, and parse the step-report-json container output for structured violations grouped by rule code.
  • Use Case: A PR on openshift/hypershift shows a failing enterprise-contract check. Use this Skill to locate the archived PipelineRun, pull the EC JSON report, and get the exact violation codes, messages, and suggested fixes such as updating task digests in .tekton/ files.

Quick Start

Find the failing enterprise contract check on my pull request and show me the violations from the archived Konflux PipelineRun.

Frequently Asked Questions about Konflux Archived PipelineRuns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I access a Konflux PipelineRun that no longer exists via oc get?

Query the KubeArchive REST API at the kubearchive API server host using your oc token for authentication. Request the PipelineRun by name under apis/tekton.dev/v1 in the crt-redhat-acm-tenant namespace to get its full archived spec and status.

How do I find enterprise contract violations from a failed Konflux check on GitHub?

Use gh api to list check-runs on the PR head commit, filter for failing enterprise-contract checks, and extract the PipelineRun name from the output text. Then fetch the archived EC task pod's step-report-json container log, which contains structured violations with rule codes and solutions.

How do I get pod logs from a completed Konflux TaskRun?

List archived pods via KubeArchive with the label selector tekton.dev/taskRun set to the TaskRun name, then request the pod log endpoint with a specific container name. Container names come from the pod spec's initContainers and containers fields.

Why does KubeArchive return 404 for my PipelineRun?

A 404 means the resource may not be archived yet, so try oc get directly in the crt-redhat-acm-tenant namespace first. Also confirm you are logged in to the correct cluster, api.stone-prd-rh01.pg1f.p1.openshiftapps.com:6443.

What does the trusted_task.trusted violation mean in Konflux EC checks?

It means a task version in your pipeline is not in the trusted task list. The violation message includes the required SHA, and the fix is updating the task digests in your .tekton/ pipeline files to the trusted version.