Pre Kubernetes v1.20, exec livenessprobes `timeoutSeconds` wasn't functional, and defaults to 1 second. The livenessprobe for the scheduler, however, takes longer than 1 second to finish so the scheduler will have consistent livenessprobe failures when running on v1.20.

> Before Kubernetes 1.20, the field timeoutSeconds was not respected for exec probes: probes continued running indefinitely, even past their configured deadline, until a result was returned.

```
...
  Warning  Unhealthy  23s    kubelet            Liveness probe failed:
```

https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes

**Kubernetes version**: v1.20.2

**What happened**:

Livenessprobe failures keeps restarting the scheduler due to timing out.

**What you expected to happen**:

Livenessprobe succeeds.

**How to reproduce it**:

Deploy the helm chart on v1.20+ with the default livenessprobe `timeoutSeconds` of 1 and watch the scheduler livenessprobe fail.

chart/tests/test_scheduler.py
#
#
import unittest
import jmespath
from parameterized import parameterized
from tests.helm_template_generator import render_chart
class SchedulerTest(unittest.TestCase):
    @parameterized.expand(
        [
            ("CeleryExecutor", False, "Deployment"),
            ("CeleryExecutor", True, "Deployment"),
            ("CeleryKubernetesExecutor", True, "Deployment"),
            ("KubernetesExecutor", True, "Deployment"),
            ("LocalExecutor", True, "StatefulSet"),
            ("LocalExecutor", False, "Deployment"),
        ]
    )
    def test_scheduler_kind(self, executor, persistence, kind):