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.
Apache License 2.0
51
stars
18
forks
source link
Add requireSameNode field for pod dependencies #32
Previously pod dependencies always required the pod to be on the same
node. Though this was documented it often did not match user intuition
as merely depending on a pod shouldn't require anything more than it
existing somewhere in the cluster. This adds a field to pod
dependencies to specify whether the pod is required to be on the same
node. This defaults to false for the reasons above, which is a breaking
change.
PiotrProkop
commented
6 years ago
Previously pod dependencies always required the pod to be on the same node. Though this was documented it often did not match user intuition as merely depending on a pod shouldn't require anything more than it existing somewhere in the cluster. This adds a field to pod dependencies to specify whether the pod is required to be on the same node. This defaults to false for the reasons above, which is a breaking change.