[FEATURE] Native Gateway API HTTPRoute support in kagent-tools Helm chart #80

Summary

The kagent-tools Helm chart currently ships service.yaml but no route/ingress resource. Please add native Gateway API HTTPRoute support to the chart.

Motivation

Clusters that have moved from Ingress to Gateway API have no supported way to expose the tools server through the chart. Today the only options are:

• maintaining a templates/httproute.yaml in a fork/overlay of the chart, or
• managing a separate HTTPRoute manifest outside Helm

Both drift from the chart on every upstream bump, and neither can reuse _helpers.tpl naming, labels, or the service.ports.tools port. Supporting HTTPRoute natively in the upstream chart keeps route naming, labels, and the backend service reference in sync with the rest of the chart automatically, which raises chart quality over the long run — rather than every user re-implementing the same template locally.

Proposal

Add templates/httproute.yaml guarded by a new values block, rendered only when explicitly enabled so existing installs are unaffected:

httpRoute:
  enabled: false
  annotations: {}
  labels: {}
  parentRefs: []
    # - name: my-gateway
    #   namespace: gateway-system
    #   sectionName: https
  hostnames: []
    # - tools.example.com
  rules: []
    # optional override; defaults to a single rule routing "/" to the tools service port

Notes:

• Backend ref should default to the chart's own service name (include "kagent-tools.fullname") and service.ports.tools.port, so it stays correct through renames.
• apiVersion: gateway.networking.k8s.io/v1.
• Ship a tests/httproute_test.yaml case alongside the existing deployment_test.yaml / rbac_test.yaml helm-unittest suites.

Happy to open a PR if the direction looks good.