stacklok / toolhive / 24159722743

65%

Build Type

push

github

Committed by web-flow

Commit Message

Align MCPRegistry CRD with registry server v2 config format (#4653)

* Align MCPRegistry CRD with registry server v2 config format

The registry server has moved to a v2 config format that separates data
sources from registry views, adds claims-based authorization, and
supports managed and Kubernetes source types. The operator's MCPRegistry
CRD was still generating v1 config (flat registries[] with inline source
configs), meaning operators deploying via the CRD got none of the v2
authorization features.

This updates the CRD spec to use separate sources[] and registries[]
fields, adds support for claims (apiextensionsv1.JSON), authz roles,
managed sources, Kubernetes sources with namespace selectors, and public
paths on auth config. The config generator now produces v2-compatible
YAML that the registry server can consume directly.

A default Kubernetes source is auto-injected when the user defines none,
preserving backward compatibility for MCP server discovery.

Closes #4572

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Regenerate CRD API reference docs

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Remove auto-injection of default Kubernetes source

Users should explicitly define all sources in their MCPRegistry spec,
including Kubernetes discovery sources. The auto-injection was adding
implicit behavior that would be surprising when combined with
claims-based authorization.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Add MaxMetaSize, DynamicAuth, and Telemetry to MCPRegistry CRD

Add remaining v2 config fields to achieve full parity with the registry
server configuration format:

- MaxMetaSize (*int32) on DatabaseConfig for controlling metadata size
  limits
- DynamicAuth with AWS RDS IAM support on DatabaseConfig for short-lived
  database credentials
- TelemetryConfig on MCPRegistrySpec for OpenTelemetry configuration
  with tracing (sampling rate) and metrics sub-c... (continued)

Coverage Stats

114 of 524 new or added lines in 4 files covered. (21.76%)

48 existing lines in 7 files now uncovered.

54922 of 84596 relevant lines covered (64.92%)

61.54 hits per line