initial commit

deploy/k8s/agentgateway-backend.yaml

@@ -0,0 +1,41 @@
+# AgentgatewayBackend for captcha-solver-mcp.
+#
+# Two options for getting this into the cluster — pick one:
+#
+#  A) Hand-written: drop this file into
+#     home-cluster/kubernetes/namespaces/agentgateway-system/base/mcp-servers/captcha-solver/agentgateway-backend.yaml
+#     and add it to the kustomization.yaml alongside deployment.yaml/service.yaml.
+#
+#  B) Generated by the agentgw-cfg chart: add an entry to the `mcpServers` list
+#     in home-cluster/kubernetes/namespaces/agentgateway-system/agentgw-cfg/values.yaml:
+#
+#       mcpServers:
+#         - name: captcha-solver
+#           host: mcp-captcha-solver.agentgateway-system.svc.cluster.local
+#           port: 8085
+#           # path: /mcp (default)
+#           # protocol: StreamableHTTP (default)
+#
+#     This produces BOTH a per-server AgentgatewayBackend (matching the file
+#     below) AND a per-server HTTPRoute at /mcp/captcha-solver. The chart
+#     template lives at:
+#       home-cluster/kubernetes/namespaces/agentgateway-system/agentgw-cfg/templates/mcp.yaml
+#
+# Option B is preferred (matches the existing per-server backends) unless you
+# also need to attach AgentgatewayPolicy/auth that the chart doesn't expose.
+---
+apiVersion: agentgateway.dev/v1alpha1
+kind: AgentgatewayBackend
+metadata:
+  name: mcp-captcha-solver
+  namespace: agentgateway-system
+spec:
+  mcp:
+    sessionRouting: Stateless
+    targets:
+      - name: captcha-solver
+        static:
+          host: mcp-captcha-solver.agentgateway-system.svc.cluster.local
+          path: /mcp
+          port: 8085
+          protocol: StreamableHTTP