MCPGateway

The MCPGateway resource defines the gateway deployment that serves as the entry point for all MCP traffic.

Purpose

MCPGateway creates and manages:

  • A Deployment running the gateway proxy
  • A Service exposing the gateway
  • An Ingress for external access (optional)

Example

apiVersion: mcp-gateway.ohcs.io/v1alpha1
kind: MCPGateway
metadata:
  name: my-gateway
  namespace: default
spec:
  domain: mcp.example.com
  replicas: 2
  tls:
    enabled: true
    clusterIssuer: letsencrypt-prod

Key Fields

spec.domain

The domain name for the gateway. Used to configure the Ingress host.

spec.replicas

Number of gateway pod replicas. Defaults to 1.

spec.tls

TLS configuration for the Ingress:

  • enabled: Whether to enable TLS
  • clusterIssuer: cert-manager ClusterIssuer name
  • secretName: Existing TLS secret (alternative to clusterIssuer)

spec.ingressClassName

Ingress class to use (e.g., nginx, traefik).

spec.resources

Resource requests and limits for the gateway container.

Status

The MCPGateway status reflects the current state:

status:
  conditions:
  - type: Ready
    status: "True"
    reason: DeploymentReady
    message: Gateway deployment is ready
  endpoints:
  - https://mcp.example.com
Edit this page on GitLab