-
Notifications
You must be signed in to change notification settings - Fork 2
Add docs about Registry deployment via Operator #386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
blkt
wants to merge
2
commits into
main
Choose a base branch
from
docs/registry-operator-docs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+752
−15
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.
|
ChrisJBurns
reviewed
Dec 10, 2025
Contributor
Author
|
@ChrisJBurns thanks for the review, I should have addressed all your comments, PTAL. |
431ed5d to
e95c212
Compare
e95c212 to
10752e8
Compare
This change adds how to use the Operator to deploy a Registry Server instance. Specifically, documentation under `docs/toolhive/guides-registry` only mentions that you can use the Operator to deploy a Registry Server instance and links back to a page under `docs/toolhive/guides-k8s` containing all the documentation. Documentation about using Postgres password file is not there because we're working to make that transparent to the User. I left documentation using plain Kubernetes resources untouched in the `docs/toolhive/guides-registry` guide.
10752e8 to
05ba6a6
Compare
rdimitrov
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This change adds how to use the Operator to deploy a Registry Server instance. Specifically, documentation under
docs/toolhive/guides-registryonly mentions that you can use the Operator to deploy a Registry Server instance and links back to a page underdocs/toolhive/guides-k8scontaining all the documentation.Documentation about using Postgres password file is not there because we're working to make that transparent to the User.
I left documentation using plain Kubernetes resources untouched in the
docs/toolhive/guides-registryguide.Type of change
Related issues/PRs
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