Describe the Bug
there is no way to directly get the job that acted on a nodepool/cluster resource. One would always have to go through the list of jobs, and filter by label. It is a very trivial operation, and we need it in order to show logs of those operations on kloudlite web dashboard.
Also, there must be a kloudlite.io/job_name annotation on the created job, as this is required for ingesting it's logs in our loki
Expected Behavior
job name, and job namespace must be somewhere in the resource spec, so that they are discoverable, without any label magic
Thanks!
Describe the Bug
there is no way to directly get the job that acted on a nodepool/cluster resource. One would always have to go through the list of jobs, and filter by label. It is a very trivial operation, and we need it in order to show logs of those operations on kloudlite web dashboard.
Also, there must be a
kloudlite.io/job_nameannotation on the created job, as this is required for ingesting it's logs in our lokiExpected Behavior
job name, and job namespace must be somewhere in the resource spec, so that they are discoverable, without any label magic
Thanks!