For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.
Advanced settings
Configure advanced settings for Solo Enterprise for agentregistry.
Limit UI runtime displays
By default, the Solo Enterprise for agentregistry UI allows you to create all types of runtimes, including agentcore, kagent, virtual, foundry, and copilotstudio. You can restrict the types of runtimes that you want to display in the UI by using the enabledRuntimes in your Helm values file.
Note
The enabledRuntimes Helm value affects two UI surfaces only: the runtime type tabs in the Add Runtime Connection wizard, and the runtime type filter on the deployments page. You are still able to see restricted runtimes that you already connected in the Runtime view and view deployed instances from a restricted runtime in the Instances view.
Upgrade the Helm release to limit the runtime display in the UI. The following command only allows the AWS Bedrock AgentCore and Microsoft Copilot Studio runtimes to be displayed in the UI.
helm upgrade -i agentregistry \ oci://us-docker.pkg.dev/solo-public/agentregistry-enterprise/helm/agentregistry-enterprise \ --namespace agentregistry-system \ --reuse-values \ --set "config.enabledRuntimes={agentcore,copilotstudio}"Open the Solo Enterprise for agentregistry UI. Verify that only the specified runtime types appear in the Add Runtime Connection wizard and when trying to deploy an agent to a runtime.