Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-20485

expose kubernetes node name/etc. in jenkins build logs

    Details

      Description

      At present, when jenkins build failures are suspected to be caused by a specific kubernetes node, the process for determining the node name is tedious. It requires determining the name of the jenkins agent(s) the build was scheduled upon, then manually describing the running k8s pod(s) to see which node(s) said pod(s) are currently scheduled on. If the pod(s) have been killed/restarted since the suspect build, this information is essentially lost to the SQRE team (but perhaps could be reverse engineered from kubelet logs?)

        Attachments

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              jhoblitt Joshua Hoblitt
              Watchers:
              Adam Thornton, Joshua Hoblitt
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel