From 36ce856906010e3c7e978bea1b1b31187381e166 Mon Sep 17 00:00:00 2001 From: Enrique Gonzalez Date: Fri, 6 Nov 2026 19:39:30 +0000 Subject: [PATCH] Say Cloud executors can reach private registries via Private Connectivity Cloud-managed executors for auto-indexing and server-side Batch Changes use the same Private Connectivity methods as private code hosts, so their jobs can pull from internal package and container registries. The Private Connectivity section now says so, and the Customer-managed executors section points out that Private Connectivity usually covers registry access without running your own executors. Co-authored-by: Amp Amp-Thread-ID: https://ampcode.com/threads/T-c2c49e6a-8194-4e78-9204-53c7b947eca6 --- docs/cloud/index.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/cloud/index.mdx b/docs/cloud/index.mdx index 3d959a369..4435ec99b 100644 --- a/docs/cloud/index.mdx +++ b/docs/cloud/index.mdx @@ -118,11 +118,13 @@ For unsupported private connectivity methods, Sourcegraph offers connectivity vi - [Private Resources exposed via alternate public load balancers](/cloud/private-connectivity-public-lb) +The Cloud-managed executors that run [precise auto-indexing](/code-navigation/auto-indexing) and [server-side Batch Changes](/batch-changes/server-side) use the same connections, so their jobs can pull from internal package and container registries such as Nexus, Artifactory, npm, or private Docker registries. Expose the registry through one of the methods above, and tell your account team the hostname that jobs pull from and the ports the registry uses. The Sourcegraph Cloud team configures routing for it as it does for a private code host. + ### Customer-managed executors Sourcegraph Cloud runs the [executors](/admin/executors) for [server-side Batch Changes](/batch-changes/server-side) and [precise auto-indexing](/code-navigation/auto-indexing) for you, in your instance's dedicated network. You don't need to deploy or configure executor infrastructure. -If your organization needs to run executors in its own Google Cloud or AWS account instead, ask your Sourcegraph account team about customer-managed executors. The Sourcegraph Cloud team reviews each request with you before enabling it. Customer-managed executors are separate from [Private Connectivity](#private-connectivity), which connects your instance to private code hosts and other resources. +If your organization needs to run executors in its own Google Cloud or AWS account instead, ask your Sourcegraph account team about customer-managed executors. The Sourcegraph Cloud team reviews each request with you before enabling it. Customer-managed executors are separate from [Private Connectivity](#private-connectivity). If your executor jobs only need to reach internal package or container registries, Private Connectivity usually covers that with Cloud-managed executors. Customer-managed executors use the same Terraform modules as self-hosted Sourcegraph instances. Follow the deployment guide for [Google Cloud](/self-hosted/executors/deploy-executors-terraform-gcp) or [AWS](/self-hosted/executors/deploy-executors-terraform-aws).