Prow Job Editor

Job Configuration

Job Type *

Repository *

Job Name *

Branch Name Optional: Base branch for the job

📦 Release Job Generator PERIODIC

Release Branch * Must match pattern: release-X.Y.Z or release-X.Y.Z-rc.N

📋 Select Jobs

Loading jobs...

📋 0 of 0 jobs selected

Custom Job Configuration

Paste a job configuration that is not yet part of the checked in repo and generate a runnable ProwJob.

Job Type *

Repository

Job Name (optional)

Job Config YAML *

Supports a single job object or a list/map of jobs. When multiple jobs are present specify a job name above.

Debug Agent

Trigger AI-powered analysis of a JIRA support ticket. The agent fetches the ticket, downloads log bundles, clones source code, and posts the analysis back to JIRA.

JIRA Ticket *

TVK Version Leave blank to auto-detect from the JIRA ticket

Select repos to add to the context

k8s-triliovault k8s-commons (submodule of k8s-triliovault) k8s-triliovault-operator s3-fuse-plugin

k8s-commons is a submodule of k8s-triliovault; selecting it requires k8s-triliovault.

Custom Prompt

You are debugging a customer-reported issue for the codebase in this workspace (folder: k8s-triliovault).
The workspace also contains attachments/ with Trilio log bundle(s). Treat attachments/ as primary evidence for debugging (along with @issue.txt and source code). Reference @attachments in context whenever analyzing logs.

Important: The issue may be invalid or unrelated to TrilioVault; if so, your primary deliverable is an evidence-backed analysis explaining why it is invalid or out of scope.

--- Inputs (read in this order) ---

1. @issue.txt – extract expected vs observed behavior, exact error strings, environment versions, repro steps, and impacted components.
2. @attachments/ – locate the relevant bundle(s) and extract signals: operator/controller logs, Kubernetes events, CR YAMLs, pod describe output, API-server errors, storage/CSI errors, and timestamps. Build a concise timeline of what happened.
3. Repo code (k8s-triliovault/) – map the extracted errors to code paths (controllers/reconcilers, webhooks, CRDs, Helm manifests, version/feature gates).

--- Debugging method (must follow) ---

- Generate 3-5 hypotheses first; for each, specify what log evidence in attachments/ would confirm or deny it.
- Do NOT propose speculative fixes before passing the validity gate below.
- Prefer narrowing by timestamp correlation and resource correlation (namespace, pod name, CR name, reconcile IDs).

--- Required outputs (always) ---

1. Validity assessment – decide one of:
   (A) Valid Trilio issue
   (B) Invalid / misconfiguration
   (C) External dependency issue (Kubernetes, storage, network)
   (D) Insufficient data
   Use attachments/ as the main evidence and cite exact log excerpts, filenames, timestamps, and involved resources.

2. RCA / Invalidity analysis:
   - If (A): identify failing code path and first incorrect assumption or data; include file paths and functions; tie directly to log evidence.
   - If (B) or (C): explain why Trilio is not root cause; identify likely fault domain and supporting log evidence (e.g. RBAC denies, API timeouts, CSI mount failures).
   - If (D): list exactly what is missing from attachments/ and why it blocks a conclusion.

3. Needed from customer – targeted questions only; prefer "please provide X file or command output" that would exist in the bundle but is missing.

--- Optional outputs (only if validity = A and evidence is sufficient) ---

4. Workaround – minimal-risk mitigation steps.
5. Ideal fix – proposed code or config change, backward-compatibility notes, and test plan.

--- Output format ---

Structure the response with these sections in order:
  "Validity assessment"
  "RCA / Invalidity analysis"
  "Needed from customer"
  "Workaround" (optional)
  "Ideal fix" (optional)

Modify the prompt sent to the AI agent. The default prompt is pre-filled above.

📝 ProwJob Configuration

📋 Container Form 📄 YAML View

🐳 Container Configuration

Edit container settings below. Changes will sync to the YAML view.

⚠️

Generate or load a ProwJob YAML first to edit container settings.

🛡️ Protect from Auto-Abort Add prow.k8s.io/skip: 'true' to exclude from skip-periodics auto-abort

Select Container

🖼️ Image * Container image to use

⚡ Command Comma-separated command (entrypoint override)

📝 Args Arguments to the command (one per line)

📊 Resources

🔲 Request CPU

💾 Request Memory

🔲 Limit CPU

💾 Limit Memory

🔒 Security Context

Privileged Run container in privileged mode

Run as Root (UID 0) Run as root user

🌍 Environment Variables

🔄 Auto-sync enabled

Configure job settings above and click "Get YAML" to generate the ProwJob configuration

🚀 Prow Job Editor