When Kerberos is enabled, the sidecar container that renews the Kerberos ticket never stops running, because the file /krb5_cache/status_file that is used to stop it is never created. This means that the job-controller pod is kept in a Terminating status for a long time, until the Kubernetes deadline is reached.
When Kerberos is enabled, the sidecar container that renews the Kerberos ticket never stops running, because the file
/krb5_cache/status_filethat is used to stop it is never created. This means that the job-controller pod is kept in aTerminatingstatus for a long time, until the Kubernetes deadline is reached.