- Proof of concept only. The repo demonstrates a potential agent contract and operator flow; it is not production ready.
- Mock agents. All agents in
mock_agent/are synthetic services to illustrate the deployment and discovery contract we intend to enforce. - Security/integration gaps. Auth, RBAC, hardened reconcilers, and polished docs are still in flight.
- The core features here overlap with Kagenti, we are investigating implementing the features demonstrated here via integration between Kagenti and OpenShift. See: Issue #12
- Turning agent workloads into first-class Kubernetes resources via an
AgentCRD and controller. - Defining a uniform runtime contract (
/.well-known/agent.json,/healthz,/metrics) that any compliant agent image must satisfy. - Bridging OpenShift agents into developer tooling through an MCP server that discovers agents and relays A2A protocol messages.
- Install the Agent CRD and demo operator:
cd agent-operator && oc apply -f agent-crd.yaml(plus the controller manifest once hardened). - Deploy a mock agent:
cd mock_agent && ./deploy.sh <AGENT_NAME>(names map to files inmock_agent/data/). - Verify discovery via
oc get agentsand interact through the MCP bridge. - Optionally, clean up with
mock_agent/teardown.sh.
- Install Python 3.13+ and uv or
pip. - Run
uv sync(orpip install -e .) to pull dependencies. - Start the MCP bridge:
cd mcp && python oc_agent_bridge.py. - Use the bridge with your IDE or CLI (e.g.
claude mcp add) to list and message the mock agents.
⚠️ Treat all cluster steps as disposable demos. Hardened manifests, RBAC, and signing workflows are still future work.
- Discover mock agents labeled with
ai.openshift.io/agent.*and surface their cards. - Enforce the draft endpoint contract through deployment scripts and sample responses.
- Relay user messages to mock agents via the A2A protocol using the MCP bridge.
- Security & trust foundations (TLS, signed cards, RBAC).
- Operator hardening (stateful reconciliation, OLM packaging).
- Conformance tooling and reusable agent base images.
- Architecture and positioning slides:
docs/presentations/demo/. - Design overview and goals:
docs/README.md.
This is an exploratory project, file issues or PRs to discuss the contract, operator shape, or feature expectations.