Epic Goal

Deliver an integrated OpenShift Builds + MCP Server capability that enables secure, scalable, and intelligent build orchestration across clusters. The goal is to provide developers with flexible build strategies while empowering operators with automation, compliance, and observability through the MCP control plane.

Why is this important?

• Velocity & Flexibility: Developers can choose the right build abstraction (Dockerfile, Buildpacks, Shipwright, etc.) without sacrificing security or scalability.

• Intelligent Orchestration: The MCP Server coordinates multiple agents, ensuring workflows execute reliably with built-in verification and automated pass/fail outcomes.

• Enterprise Readiness: Features such as compliance, provenance, and CI/CD automation provide enterprises with confidence to deliver faster and safer.

• Operational Excellence: Support for automation, observability, and release enablement reduces toil for platform teams and accelerates adoption.

Scenarios

1. Developer: Pushes code → OpenShift Builds automatically transforms it into a container image with full audit trail.

       *       2. {}Operator{*}: MCP Server provisions resources, verifies build completion, and ensures compliance guardrails are applied.

       3. Release Engineer: Uses the release enablement guides to upgrade from existing builds operator to MCP-enabled workflows.

       4. SRE/Support: Receives training + docs to troubleshoot and operate MCP-enabled OpenShift Builds in production.

       5.  Automation: CI pipelines run builds end-to-end with automated tests, logs, and notifications.

Acceptance Criteria (Mandatory)

• CI – MUST be running successfully with automated tests for all supported build strategies and MCP workflows.

• Release Technical Enablement – Provide detailed documentation, upgrade guides, and feature enablement playbooks.

• Docs & Guides – User-facing docs published (Dev + Ops), including MCP Server configuration, troubleshooting, and build strategy usage.

• E2E Automation – User journey automation validated across supported scenarios.

• SRE/Support Enablement – Training material and operational runbooks delivered.

Open Questions

• How do we handle multi-cluster MCP orchestration vs. single-cluster?

• Do we need performance/scale benchmarks for MCP-enabled builds ?

• What level of FIPS/compliance validation is mandatory for GA?

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment