Update quickstarts, install, and CLI reference - #41
Merged
Conversation
Signed-off-by: Nadine2016 <nadine.spies@solo.io>
Deploying website with
|
| Latest commit: |
307df16
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5bf43409.website-1n3.pages.dev |
| Branch Preview URL: | https://oss-updates1.website-1n3.pages.dev |
Comment on lines
+17
to
+18
| - agentregistry installed with Docker Compose. See the [Install with Docker](/docs/install/docker) guide. | ||
| - An external PostgreSQL instance (version 14 or later) reachable from your Docker host. |
Contributor
There was a problem hiding this comment.
I think these need to be reworded into steps or needs a line before these
| 3. Update `AGENT_REGISTRY_DATABASE_URL` in the `agentregistry` service to point at your external database. | ||
| 4. Remove the `depends_on` condition that references the bundled postgres service. | ||
|
|
||
| The updated `agentregistry` service should look like this: |
Contributor
There was a problem hiding this comment.
Suggested change
| The updated `agentregistry` service should look like this: | |
| The updated `agentregistry` service looks like the following example: |
| ``` | ||
|
|
||
| ### Step 3: Restart the stack | ||
|
|
Contributor
There was a problem hiding this comment.
needs some kind of step wording
|
|
||
| ## Kubernetes | ||
|
|
||
| If you installed agentregistry with Helm, the instructions below show how to provision an [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/) instance in the same VPC as your EKS cluster and configure agentregistry to use it. |
Contributor
There was a problem hiding this comment.
Suggested change
| If you installed agentregistry with Helm, the instructions below show how to provision an [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/) instance in the same VPC as your EKS cluster and configure agentregistry to use it. | |
| If you installed agentregistry with Helm, the instructions in this section show how to provision an [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/) instance in the same VPC as your EKS cluster and configure agentregistry to use it. |
| If you installed agentregistry with Helm, the instructions below show how to provision an [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/) instance in the same VPC as your EKS cluster and configure agentregistry to use it. | ||
|
|
||
| ### Before you begin | ||
|
|
|
|
||
| ### Step 2: Create the agentregistry database | ||
|
|
||
| Run a temporary pod in your cluster to connect to the RDS instance and create the application database. |
Contributor
There was a problem hiding this comment.
all in this section needs to be formatted into standard steps
|
|
||
| ### Step 5: Verify the connection | ||
|
|
||
| 1. Verify the pods are healthy and that no bundled `agentregistry-postgresql-*` pod is running. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. Verify the pods are healthy and that no bundled `agentregistry-postgresql-*` pod is running. | |
| 1. Verify that the pods are healthy and that no bundled `agentregistry-postgresql-*` pod is running. |
| kubectl -n agentregistry run pg-check --rm -it --image=postgres:16 --restart=Never -- \ | ||
| psql "host=$PG_HOST port=$PG_PORT user=$PG_USER password='$PG_PASS' dbname=agentregistry sslmode=require" \ | ||
| -c '\dt' | ||
| ``` |
Contributor
There was a problem hiding this comment.
maybe an example output? idk what they need to look for in the tables
| | sed -n '/AGENT_REGISTRY_DATABASE_URL/,/^$/p' | head -5 | ||
| ``` | ||
|
|
||
| Expected output: |
Contributor
There was a problem hiding this comment.
Suggested change
| Expected output: | |
| Example output: |
| kubectl -n agentregistry logs deploy/agentregistry-server --tail=50 | grep "migration" | ||
| ``` | ||
|
|
||
| Expected output: |
Contributor
There was a problem hiding this comment.
Suggested change
| Expected output: | |
| Example output: |
Signed-off-by: Nadine2016 <nadine.spies@solo.io>
1 task
Rachael-Graham
approved these changes
Aug 18, 2026
Signed-off-by: Nadine2016 <nadine.spies@solo.io>
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
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.
No description provided.