Differential D4920 Diff 28838 docs/next/src/pages/deploying/k8s_part2.mdx

Changeset View

Standalone View

docs/next/src/pages/deploying/k8s_part2.mdx

	Show All 36 Lines
	during deploys).			during deploys).

	The motivation for adding the Dagster K8sScheduler implementation is to enable users to have			The motivation for adding the Dagster K8sScheduler implementation is to enable users to have
	multiple Dagit Pods in the Deployment without the risk of duplicate pipeline runs or missing pipeline runs.			multiple Dagit Pods in the Deployment without the risk of duplicate pipeline runs or missing pipeline runs.
	We increase the robustness of the scheduler by leveraging native Kubernetes objects.			We increase the robustness of the scheduler by leveraging native Kubernetes objects.

	### How to enable:			### How to enable:

	In order to enable the Dagster K8sScheduler, set `scheduler.k8sEnabled` to `true` in the Helm			In order to enable the Dagster K8sScheduler, set `scheduler.type` to `K8sScheduler` in the Helm
	[`values.yaml`](https://github.com/dagster-io/dagster/blob/master/helm/dagster/values.yaml)			[`values.yaml`](https://github.com/dagster-io/dagster/blob/master/helm/dagster/values.yaml)
	file and fill in the other fields in the `scheduler` section.			file and fill in the other fields in the `scheduler.config.k8sScheduler` section.

	### How it works:			### How it works:

	When a new schedule is turned on, we will create a corresponding Kubernetes CronJob object. When a			When a new schedule is turned on, we will create a corresponding Kubernetes CronJob object. When a
	schedule is updated, we will find and patch the existing CronJob so that there is no downtime. At			schedule is updated, we will find and patch the existing CronJob so that there is no downtime. At
	execution time, the Kubernetes CronJob will create a Kubernetes Job specifically to instantiate			execution time, the Kubernetes CronJob will create a Kubernetes Job specifically to instantiate
	the Run Launcher, which in turn creates the Run Coordinator Job. Kubernetes CronJob names are generated by			the Run Launcher, which in turn creates the Run Coordinator Job. Kubernetes CronJob names are generated by
	hashing the schedule properties, so different repositories can create schedules that have the same			hashing the schedule properties, so different repositories can create schedules that have the same
	▲ Show 20 Lines • Show All 42 Lines • Show Last 20 Lines