fix(jobs): jobs termination after CP restart

[jakubdyszkiewicz]

Checklist prior to review

Fix jobs termination in case of CP missing update event (like CP restart etc.)

I tested it by applying this

apiVersion: batch/v1
kind: Job
metadata:
  name: pi-2
  namespace: kuma-demo
spec:
  template:
    spec:
      containers:
      - name: ubuntu
        image: ubuntu:latest
        command: [ "/bin/bash", "-c", "--" ]
        args: [ "sleep 60" ]
      restartPolicy: Never
  backoffLimit: 4

then scaling CP down

kubectl scale deployments -n kuma-system kuma-control-plane --replicas=0

then up

kubectl scale deployments -n kuma-system kuma-control-plane --replicas=1

without this fix, the job stays running.

I'd love write E2E test for it, but it requires CP restart so it would land in non-env tests and it would be a time-consuming test.

• Link to relevant issue as well as docs and UI issues --
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s) --
  • Don't forget ci/ labels to run additional/fewer tests
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label) --

[github-actions]

backporting to release-2.4 with action

backporting to release-2.5 with action
backporting to release-2.6 with action

[github-actions]

backporting to release-2.3 with action