Skip to content
Latest (currently 2026.7.0) has the newest features, bug fixes, and CVE patches of Solo Enterprise for agentregistry.

Publish to catalog

Page as Markdown
Add your agent to the Solo Enterprise for agentregistry catalog so that you can start deploying the agent to connected providers.
About the registry catalog

Solo Enterprise for agentregistry serves as a catalog for your AI artifacts, including agents, skills, and MCP servers. You can decide which agents you want to make available to your registry users by adding them to the registry catalog. After an agent is published in the catalog, registry users can deploy them to a connected provider.
Before you can add an agent to the catalog, you must either build a Docker container image and push it to your container image registry or store the agent’s source code in a GitHub repository. The method that you need to use depends on the type of provider that you plan to deploy your agent to.
Deployment targetExample providerDocker image vs. GitHub repo
AI runtimes in KubernetesSolo Enterprise for kagentBuild the Docker container image and push it to a container registry.
Agentic cloud platformsAWS Bedrock AgentCoreStore the Dockerfile and source code in a GitHub repository.
The Docker image and GitHub repository locations are stored in the agent.yaml file that is automatically created with an agent scaffold and represents the agent definition. Note that if you did not create the agent by using the built-in scaffolding capability in Solo Enterprise for agentregistry, you must create the agent.yaml file yourself to describe the agent that you want to add to the catalog.
Before you begin

  1. Create an agent.
  2. Build Docker image or store source code.
Add the agent to the catalog

  1. Port-forward the Solo Enterprise for agentregistry controller.
    kubectl -n agentregistry-system port-forward svc/agentregistry-enterprise-server 12121:12121
  2. Open the Solo Enterprise for agentregistry catalog and click +Create > Agent.
  3. Fill out your agent definition.
    • Basic information: Enter a name and description for your agent. Add the container image location and version that you want to use. Then, click Next.
    • Technical details: Enter the language, framework, provider and model that your agent uses. Then, click Next.
    • Repository: Add the GitHub or GitLab repository that stores the source code and Dockerfile for your agent. Then, click Register Agent. If the repository is private, make sure that you have configured your credentials first, otherwise the registry cannot pre-fill this form from the repository manifest.
  4. Verify that the agent is added to the Solo Enterprise for agentregistry catalog.
  1. Review your agent.yaml definition and make any necessary changes. The following example defines both a Docker container image and GitHub repository location.
    • Docker image location (spec.source.image): By default, the arctl init command creates a scaffold that uses a local Docker container registry reference (localhost:5001/myagent) and latest tag. However, the image is not automatically pushed to this location and therefore cannot be pulled by Solo Enterprise for agentregistry during a deployment. To deploy an agent to a Kubernetes provider, such as Solo Enterprise for kagent, you must push the image to a Docker container registry and update the agent.yaml file with that location. To build the image, follow the steps in Build the Docker container image.
    • GitHub repository (spec.source.repository): By default, the arctl init command does not add a GitHub repository reference to the agent.yaml file. To deploy your agent to an agentic cloud platform, you must push the agent source code and Dockerfile to a GitHub repository and add the repository URL to your agent.yaml file as shown in this example. For testing purposes, you can use the https://github.com/solo-io/doc-examples GitHub repository. To store the source code in your own GitHub repository, follow the steps in Store the Dockerfile and source code.
    cat myagent/agent.yaml
    Example output:
    apiVersion: ar.dev/v1alpha1
kind: Agent
metadata:
    name: myagent
spec:
    source:
       image: localhost:5001/myagent:latest
       repository:
         url: https://github.com/solo-io/doc-examples
         subfolder: agentregistry/myagent
    modelProvider: gemini
    modelName: gemini-2.5-flash
    description: myagent agent
  2. Add the agent to the catalog by applying the agent definition.
    arctl apply -f myagent/agent.yaml
    Example output:
    ✓ Agent/myagent (latest) applied
  3. List the agents in your catalog.
    arctl get agents 
    Example output:
    NAME      TAG      PROVIDER   MODEL
myagent   latest   gemini     gemini-2.5-flash

Next

Now that you published the agent image, you can deploy the agent to one of the following platforms.
AWS Bedrock AgentCore
Deploy agents to AWS Bedrock AgentCore.
Solo Enterprise for kagent
Deploy your agent to an agentic runtime in Kubernetes with Solo Enterprise for kagent.
Cleanup

To delete the myagent reference from the Solo Enterprise for agentregistry catalog, use the UI or CLI.
  1. Open the agents in the Solo Enterprise for agentregistry catalog.
  2. Select the myagent agent and click Delete (trash can icon) to remove the agent from the catalog.
  1. Remove the agent from the Solo Enterprise for agentregistry catalog.
    arctl delete agent myagent --version 1.0.0
  2. Verify that the agent is removed.
    arctl get agents
Build image or store source codeDiscover and search agents