Document nested Kubernetes metadata in registry extensions #530
+14
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the ToolHive extensions schema documentation by documenting the optional kubernetes nested object within the metadata field. This metadata structure is automatically populated by the ToolHive Registry Server when it discovers MCP servers deployed in Kubernetes clusters.
Changes:
- Added explanation of the optional
kubernetesnested object within themetadatafield - Documented when this metadata appears (auto-discovered Kubernetes deployments)
- Added an example showing the
kubernetesmetadata structure in the remote server example
Update the ToolHive extensions schema documentation to document the nested kubernetes metadata structure. Add a note explaining that the kubernetes metadata is read-only and automatically added by the ToolHive Registry Server for auto-discovered Kubernetes deployments. Users should not manually add this field when creating custom registry files. Update the "Full example" section description to clarify it's for building custom registry files (input), not showing registry server output.
danbarr
approved these changes
Feb 6, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the ToolHive extensions schema documentation to document the nested kubernetes metadata structure.
Details:
metadatacan include an optionalkubernetesnested objectDescription
Type of change
Related issues/PRs
Screenshots
Submitter checklist
Content and formatting
Navigation
sidebars.ts) updated for added, deleted, reordered, or renamed filesvercel.jsonfor moved, renamed, or deleted pages (i.e., if the URL slug changed)Reviewer checklist
Content
Related to stacklok/toolhive-registry-server#490