<p>On this page <a href="https://kubernetes.io/docs/reference/using-api/api-concepts/#retrieving-large-results-sets-in-chunks" rel="nofollow noreferrer">https://kubernetes.io/docs/reference/using-api/api-concepts/#retrieving-large-results-sets-in-chunks</a>, there is a continue token that will expire after a short amount of time (by default 5 minutes).</p>
<p>I find that when kubernetes controller manager does cronjob syncall() function in my cluster, this token always expires and stops cronjob creating jobs on schedule.</p>
<p>The following is the log in kubernetes-controller-manager:</p>
<blockquote>
<p>E0826 11:26:45.441592 1 cronjob_controller.go:146] Failed to extract cronJobs list: The provided continue parameter is too old to display a consistent list result. You can start a new list without the continue parameter, or use the continue token in this response to retrieve the remainder of the results. Continuing with the provided token results in an inconsistent list - objects that were created, modified, or deleted between the time the first chunk was returned and now may show up in the list.</p>
</blockquote>
<p>So I want to know can I modify the default expired time of the continue token in Kubernetes, and how to do it?</p>
<p>Thanks.</p>

<p>This is an <a href="https://github.com/kubernetes/community/pull/896/files?short_path=0346e23#diff-0346e23dde955ef957d033a9dfa851d2" rel="nofollow noreferrer">etcd</a> default. Any auth request to etcd will incur into that 5 seconds expiry interval. This is due to the compaction interval. The good news is that you can change that as an option in the <a href="https://github.com/kubernetes-sigs/kind/issues/1436" rel="nofollow noreferrer">kube-apiserver</a> with the <code>--etcd-compaction-interval</code> option.</p>
<p>Also, it looks like doing a <a href="https://github.com/etcd-io/etcd/issues/8287#issuecomment-317566237" rel="nofollow noreferrer">simple GET within the 5 minutes</a> would actually make it extend the token timeout.</p>
<p>✌️</p>
