You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: charts/sourcegraph-executor/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
# Sourcegraph executor helm charts
2
2
3
-
This directory contains two Helm charts for deploying executors on Kubernetes. [See the docs](https://docs.sourcegraph.com/admin/executors/deploy_executors_kubernetes) for more information on executors on Kubernetes.
3
+
This directory contains two Helm charts for deploying executors on Kubernetes. [See the docs](https://sourcegraph.com/docs/self-hosted/executors/deploy-executors-kubernetes) for more information on executors on Kubernetes.
4
4
5
5
## Native Kubernetes (k8s)
6
6
This chart deploys executors that interact with the Kubernetes API to handle jobs.
7
7
8
8
> ⚠️ **Beta:** Native Kubernetes executors are in beta. For production workloads, consider deploying using
9
-
> [Terraform](https://docs.sourcegraph.com/self-hosted/executors/deploy-executors-terraform) or the
10
-
> [Linux binary](https://docs.sourcegraph.com/self-hosted/executors/deploy-executors-binary) for better long-term support.
9
+
> [Terraform](https://sourcegraph.com/docs/self-hosted/executors/deploy-executors-terraform) or the
10
+
> [Linux binary](https://sourcegraph.com/docs/self-hosted/executors/deploy-executors-binary) for better long-term support.
11
11
12
12
Your cluster will need to allow configuration of the following RBAC rules:
13
13
@@ -21,6 +21,6 @@ Your cluster will need to allow configuration of the following RBAC rules:
21
21
> ⚠️ **Beta:** Docker-in-Docker Kubernetes executors are not recommended for production use.
22
22
> This method requires privileged access to a container runtime daemon and does not use Firecracker
This chart deploys executors that deploy a [Docker in Docker](https://www.docker.com/blog/docker-can-now-run-within-docker/) sidecar with each executor pod to avoid accessing the host container runtime directly. This method requires privileged access to a container runtime daemon in order to operate correctly.
@@ -85,7 +85,7 @@ In addition to the documented values, the `executor` and `private-docker-registr
85
85
| executor.storage.class | string |`""`| StorageClass for the ephemeral volume. Only used when type is ephemeral. Defaults to the cluster default StorageClass when empty. |
86
86
| executor.storage.size | string |`""`| Size of the scratch volume. emptyDir: sets sizeLimit (optional, leave empty for unlimited). ephemeral: sets the PVC storage request (required). |
87
87
| executor.storage.type | string |`"emptyDir"`| Type of scratch volume for job workspaces. One of: emptyDir, ephemeral. emptyDir: plain emptyDir, no storage class required. ephemeral: per-pod PVC via the cluster default storage class; size is required. |
88
-
| privateDockerRegistry.enabled | bool |`true`| Whether to deploy the private registry. Only one registry is needed when deploying multiple executors. More information: https://docs.sourcegraph.com/admin/executors/deploy_executors#using-private-registries|
88
+
| privateDockerRegistry.enabled | bool |`true`| Whether to deploy the private registry. Only one registry is needed when deploying multiple executors. More information: https://sourcegraph.com/docs/self-hosted/executors/deploy-executors#using-private-registries|
89
89
| privateDockerRegistry.env | object |`{"REGISTRY_PROXY_REMOTEURL":{"value":"https://registry-1.docker.io"}}`| Extra environment variables to set on the registry container. Registry can be configured with environment variables using the pattern REGISTRY_<SECTION>_<KEY> (uppercase). Full reference: https://distribution.github.io/distribution/about/configuration To proxy an internal private registry with credentials, override REGISTRY_PROXY_REMOTEURL and supply REGISTRY_PROXY_USERNAME / REGISTRY_PROXY_PASSWORD, e.g.: env: REGISTRY_PROXY_REMOTEURL: value: https://my-internal-registry.example.com REGISTRY_PROXY_USERNAME: value: myuser REGISTRY_PROXY_PASSWORD: valueFrom: secretKeyRef: name: registry-proxy-credentials key: password |
0 commit comments