Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(runJob/kubernetes): use explicit pod name #7039

Merged
merged 2 commits into from May 22, 2019
Merged

fix(runJob/kubernetes): use explicit pod name #7039

merged 2 commits into from May 22, 2019

Commits on May 22, 2019

  1. fix(runJob/kubernetes): use explicit pod name 

    the previous implementation of run job used manifest events to get the
name of the pod created by the job. this proved unreliable as events
roll off quickly in large environments. this commit implements a
`PodNameProvider` interface which supplies `JobManifestPodLogs` with the
name of the Pod to fetch logs from. Run Job supplies these Pod names by
collecting all Pods owned by the Job. For components which are still
event based, the `JobEventBasedPodNameProvider` implements the
previously used logic for getting the Pod name from the event.
    @ethanfrogers
    ethanfrogers committed May 22, 2019
    Configuration menu
    Copy the full SHA
    4490842 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'master' into job-pod-names

    @ethanfrogers
    ethanfrogers committed May 22, 2019
    Configuration menu
    Copy the full SHA
    e3b121d View commit details
    Browse the repository at this point in the history