-
Outcome
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Product / Portfolio Work
-
74% To Do, 26% In Progress, 0% Done
-
False
-
-
False
-
None
Outcome Overview
Once all Features and/or Initiatives in this Outcome are complete, what tangible, incremental, and (ideally) measurable movement will be made toward the company's Strategic Goal(s)?
Evolve OpenShift to be an Intelligent platform with not just automation capabilities but also autonomous (goal-oriented reasoning) capabilities to enable active, goal-oriented collaboration with users and agents that autonomously manages the lifecycle, security, and optimization of cloud-native workloads with minimal human intervention.
For the initial phase, all actions will be read-only until such time that read-write actions are safeguarded and have enough guardrails to enable those capabilities or provide human in the loop interactions to enable read-write actions.
The intent is to deliver an initial set of agentic AI experiences with OpenShift 5.0 that may include the following use scenarios:
- Troubleshooting
- Installation
- Upgrade
- Observability
- Network Observability
- Security Analysis
See also Hybrid Platform Applied AI FAQ and Guidance.
Â
Success Criteria
What is the success criteria for this strategic outcome? Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.
- OCP 5: Agentic AI capabilities released with OpenShift 5 as either GA or Tech Preview. Prior to OpenShift 5, it will be strictly Tech Preview or Developer Preview.
- MCP Gateway Integration: If the Agentic AI solution depends on MCP Servers, those MCP Servers must integrate with the MCP Gateway for authn/authz, audit and control.
- Lightspeed alignment: Leverage OpenShift Lightspeed as an MCP host and align efforts to avoid duplicating any inference infrastructure.
- UXD consistency: Ensure the background/proactive pattern aligns with the overall OCP user experience design (including Patternfly) to ensure a cohesive experience for customers.
- Red Hat brand voice for chat experiences: Align chat and CLI experience to the RH brand voice.
- Telemetry: Ensure there is one or more key performance indicators (KPI) to measure the adoption and usage of the solution.
- Build: The solution must be built using Konflux.
- AI Assessment (AIA) and Privacy Impact Assessment (PIA) must be successfully completed to deliver the solution.
Â
Expected Results (what, how, when)
What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome? (possible examples: unblocking sales, shifts in product metrics, etc. {}{} provide links to metrics that will be used post-completion for review & pivot decisions). {}For each expected result, list what you will measure and +when you will measure it (ex. provide links to existing information or metrics that will be used post-completion for review and specify when you will review the measurement such as 60 days after the work is complete)
Â
Â
Post Completion Review – Actual Results
After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).
Â
- incorporates
-
CNV-64898 POC: AI Implementation in KubeVirt CI to help on failures analysis
-
- New
-
-
OSSM-9814 AI Chatbot for Kiali
-
- Closed
-
-
OCPSTRAT-2599 Unified Trust Fabric in Agentic AI Workflows
-
- New
-
-
SRVKP-8535 Transcribe Jenkinsfile to Tekton
-
- New
-
-
SRVKP-9148 Conversational Pipeline Authoring
-
- New
-
-
SRVKP-9149 Conversational Pipeline Debugger
-
- New
-
-
SRVKP-9150 Generate Pipeline for Git Repo
-
- New
-
-
OCPSTRAT-2591 [Outcome] Model Context Protocol (MCP) Gateway
-
- Refinement
-
-
OCPSTRAT-2236 AI Driven OpenShift Installation Experience (Preview)
-
- In Progress
-
-
OBSDA-1163 Insights integration with OCP Lightspeed
-
- In Progress
-
-
SRVKP-8518 Pipeline failure analysis
-
- Release Pending
-
- links to