Documentation
¶
Overview ¶
Package backend selects a sandbox provider by name, so the executor and the BYOC worker construct Docker or Kubernetes "hands" from the same config point instead of hard-coding one. Both binaries are thin glue around this: they map their environment to a Config and call New.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type Config ¶
type Config struct {
Backend string // "docker" (default) or "k8s"
// docker: empty Host falls back to DOCKER_HOST and then the well-known socket.
DockerHost string
// k8s: empty Kubeconfig and Context use in-cluster config (the executor
// running as a Deployment), then the standard kubeconfig loading rules.
K8sKubeconfig string
K8sContext string
K8sNamespace string
K8sNetSetupImage string
}
Config names the backend and carries each one's settings; only the selected backend's fields are read. An empty Backend defaults to docker — the v1 backend — so a deployment that predates this selection keeps working with no new configuration.
Source Files
Click to show internal directories.
Click to hide internal directories.