<p>I'm running the following cronjob in my minikube:</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: batch/v1
kind: CronJob
metadata:
  name: hello
spec:
  schedule: &quot;* * * * *&quot;
  concurrencyPolicy: Allow
  suspend: false
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 1
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: hello
            image: busybox
            args:
            - /bin/sh
            - somefailure
          restartPolicy: OnFailure
</code></pre>
<p>I've added the &quot;somefailure&quot; to force failing of the job. My problem is that it seems that my minikube installation (running v1.23.3) ignores <code>successfulJobsHistoryLimit</code> and <code>failedJobsHistoryLimit</code>. I've checked the documentation on <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.23/" rel="nofollow noreferrer">https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.23/</a> and it says that both parameters are available, but in the end, Kubernetes generates up to 10 jobs. When I add <code>ttlSecondsAfterFinished: 1</code>, it removes the container after 1 second, but the other parameters are completely ignored.
So I wonder if I need to enable something in minikube or if these parameters are deprecated or what's the reason why it doesn't work. Any idea?</p>

Nrgyzer
<p>It seems it's a Kubernetes bug: <a href="https://github.com/kubernetes/kubernetes/issues/53331" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/53331</a>.</p>
