seabird
seabird copied to clipboard
Better identify pods vs jobs
Summary
There's no real identification of pods vs job in the UI. It would be nice to indicate pods started by a job somehow.
Motivation
Showing clear run-once jobs vs continuing to run pods helps clarify what's going on to users. In the example below, nothing indicates the highlighted pods are job spawned.
Proposal
Kubernetes does track if pods are spawned by jobs:
kubectl describe pod/gerrit-github-sync-28588020-xbcrs
Name: gerrit-github-sync-28588020-xbcrs
Namespace: default
Priority: 0
Service Account: default
Node: XXXXXXXXX
Start Time: Thu, 09 May 2024 14:00:00 -0500
Labels: batch.kubernetes.io/controller-uid=XXXXXX
batch.kubernetes.io/job-name=gerrit-github-sync-28588020
controller-uid=62cbef6d-4306-4838-b67e-413f7f9d4da4
job-name=gerrit-github-sync-28588020
Annotations: <none>
Status: Succeeded
Providing some indication of a once-run job pod (maybe linking to the job) would be useful.