Used as a container entrypoint, it will wait for specified k8s dependencies, create files based on ConfigMaps, and much more - before running a given command.
It is a common pattern to depend on the same set of multiple jobs from
multiple places. Additionally with orchestration tools this set of job
may be dynamic based on configuration. In kubernetes we can encapsulate
this set of jobs via shared labels. This patchset then adds support to
depend on such a set of jobs via labels.
This is exposed via a new DEPENDENCY_JOBS_JSON env var, but
DEPENDENCY_JOBS is retained for backward compatibility. For consistency
DEPENDENCY_POD is renamed to DEPENDENCY_POD_JSON which is a breaking
change.
It is a common pattern to depend on the same set of multiple jobs from multiple places. Additionally with orchestration tools this set of job may be dynamic based on configuration. In kubernetes we can encapsulate this set of jobs via shared labels. This patchset then adds support to depend on such a set of jobs via labels.
This is exposed via a new DEPENDENCY_JOBS_JSON env var, but DEPENDENCY_JOBS is retained for backward compatibility. For consistency DEPENDENCY_POD is renamed to DEPENDENCY_POD_JSON which is a breaking change.