1

On this page https://kubernetes.io/docs/reference/using-api/api-concepts/#retrieving-large-results-sets-in-chunks, there is a continue token that will expire after a short amount of time (by default 5 minutes).

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.

The following is the log in kubernetes-controller-manager:

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.

So I want to know can I modify the default expired time of the continue token in Kubernetes, and how to do it?

Thanks.

Rico
  • 58,485
  • 12
  • 111
  • 141
yr12Dong
  • 21
  • 3

1 Answers1

2

This is an etcd 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 kube-apiserver with the --etcd-compaction-interval option.

Also, it looks like doing a simple GET within the 5 minutes would actually make it extend the token timeout.

✌️

Rico
  • 58,485
  • 12
  • 111
  • 141
  • Thanks Rico.At last, we decide to reduce the count of cronjob.We think modify configuration of kube-apiserver is not a good choice for kubernetes. – yr12Dong Sep 01 '20 at 10:16
  • Good to hear! If the answer is satisfactory can you accept it? Thanks. – Rico Sep 01 '20 at 14:34