NE-2447: Implement inspect_route tool

[bentito]

This PR adds the inspect_route tool to the NetEdge toolset, enabling LLMs to analyze OpenShift Route configurations.

This tool is essential for the NetEdge diagnostic capabilities as it allows the agent to verify:

• Ingress configuration (hostnames, paths, TLS termination)
• Backend service routing and weights
• Router status and admission conditions

By exposing these details, the agent can troubleshoot connectivity issues at the ingress layer.

[openshift-ci-robot]

@bentito: This pull request references NE-2447 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This PR adds the inspect_route tool to the NetEdge toolset, enabling LLMs to analyze OpenShift Route configurations.

This tool is essential for the NetEdge diagnostic capabilities as it allows the agent to verify:

• Ingress configuration (hostnames, paths, TLS termination)
• Backend service routing and weights
• Router status and admission conditions

By exposing these details, the agent can troubleshoot connectivity issues at the ingress layer.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bentito
Once this PR has been reviewed and has the lgtm label, please assign kaustubh-pande for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[matzew]

could we do grouping via testify/suite ?
e.g. similar to requested here: #131 (comment) ?

I guess we can also do that in a follow up PR, for all netedge tests.

[matzew]

looks like the actual implementation only returns the Route , not "related services".

Perhaps something like:

"Inspect an OpenShift Route to view its full configuration and status."

[bentito]

/retest

[openshift-ci]

@bentito: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/fips-image-scan-openshift-mcp-server	0d73d2e	link	true	/test fips-image-scan-openshift-mcp-server

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.