9b1b7056b0
Check the chart's actual DAGSTER_PG_PASSWORD injection in the tightly coupled preflight instead of DAGSTER_POSTGRES_*, which the Simpl chart never sets; the old check warned about a misconfiguration on a correctly configured run pod. Evidence reports the variable name only, never its value. Record the platform k8s_job_executor run as cluster-verified in the guide and readiness checklist, add the Dagster UI screenshots covering job list, graph, code-configured tags and a successful run. Changelog: fixed
1.6 KiB
1.6 KiB
0.1.0 (unreleased)
added
- Repository skeleton for the
distributed-executionsupporting data service. - User guide covering execution-target selection, decision support and readiness checks.
- Runnable tightly coupled reference implementations (
in_process,multiprocess,k8s_job_executor). - Runnable loosely coupled reference implementations via dagster-pipes
(
PipesSubprocessClient,PipesK8sClient) with a standalone external payload image. - Working example configuration and RBAC for both execution targets.
verified
tightly_coupled_k8s_jobexecuted end to end on sandbox-cat-dat through the platformK8sRunLauncher(run1d8cb167-9fb8-4a34-a036-789eac381e13), closing readiness rows T6 and T7. Step outputs are written to the shareddagster-shared-pvcby pinningfs_io_manager'sbase_dir;DAGSTER_HOMEset throughstep_k8s_configis ignored, because the Dagster chart injectsDAGSTER_HOME=/tmp/dagsterahead of it.loosely_coupled_k8s_jobreachedRUN_SUCCESSon sandbox-cat-dat through the standalone probe (runcff9b348-bfc3-4ac1-ab51-a94892b8e3a0), with four external payload pods reporting over the pod-log message channel.- Tightly coupled preflight evidence now checks the chart's actual
DAGSTER_PG_PASSWORDinjection without exposing its value. - Dagster UI screenshots cover the registered jobs, graph, code-configured execution-target tags and a successful reference run.
- The platform deployment diagram includes the service and both integration patterns.
pending
- Extend the project-level GitLab pipeline to publish the payload image as well as the code-location image.