Add quickstart smoke test to e2e suite#284
Conversation
|
@HarshithaMS005: The label(s) DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for kube-agentic-networking ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Validates quickstart policy manifests and MCP authorization (local and remote backends) in CI to catch regressions like broken allowlists. Signed-off-by: Harshitha MS <harshitha.ms@ibm.com>
0c8f3c6 to
6c63b74
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: HarshithaMS005 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
What type of PR is this?
/kind test
What this PR does / why we need it:
The quickstart guide (site-src/guides/quickstart/) is the main way users try Agentic Networking, but nothing in CI exercised those manifests end-to-end. Existing e2e tests use custom testdata/ resources and a single /mcp route, so regressions in the quickstart YAML or policy wiring (for example #272) could break the quickstart without failing CI.
This PR adds TestQuickstartE2E to the existing e2e suite. It applies the real quickstart MCP server deployment and policy/e2e.yaml (Gateway, HTTPRoutes, XBackends, XAccessPolicies), then checks MCP calls through /local/mcp and /remote/mcp match the documented allow/deny behavior. It runs in the same Kind-based e2e job (pull-kube-agentic-networking-e2e) as the other controller tests, so manifest and policy mistakes are caught before users hit them in the quickstart.
Which issue(s) this PR fixes:
Fixes #281
Does this PR introduce a user-facing change?: