Make CrashLoopBackoff timing tuneable, or add mechanism to exempt some exits
<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/). --> **Is this a BUG REPORT or FEATURE REQUEST?**: Feature request /kind feature **What happened**: As part of a development workflow, I intentionally killed a container in a pod with `restartPolicy: Always`. The plan was to do this repeatedly, as a quick way to restart the container and clear old state (and, in Minikube, to load image changes). The container went into a crash-loop backoff, making this anything but a quick option. **What you expected to happen**: I expected there so be some configuration allowing me to disable, or at least tune the timing of, the CrashLoopBackoff. **How to reproduce it (as minimally and precisely as possible)**: Create a pod with `restartPolicy: Always`, and intentionally exit a container repeatedly. **Anything else we need to know?**: I see that the backoff timing parameters are hard-coded constants here: https://github.com/kubernetes/kubernetes/blob/5f920426103085a28069a1ba3ec9b5301c19d075/pkg/kubelet/kubelet.go#L121 https://github.com/kubernetes/kubernetes/blob/5f920426103085a28069a1ba3ec9b5301c19d075/pkg/kubelet/kubelet.go#L155 One might reasonably expect these to be configurable at least at the kubelet level - say, by a setting like [these](https://github.co
Posted by jgiles on Dec 18, 2017, 1:25 AM
Tags
Related issues
- ⚠️ PHP CVEs. Update required!
- I think RTS could continue to work if someone made a massive leap of faith and put all the modern infra around it that a AAA extraction s...
- RFC: Pluggable SessionDB Provider — PostgreSQL, MySQL, and Beyond
- v2.1.113+ broken on Termux/Android: native binary requires glibc, no JS fallback
- I’m firmly anti-Tahoe and haven’t updated, and I’ve started to find Apple despicable.
- [FEATURE] Link a source control repo as the source for organization skills
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
reliability (Sysadmin)
⚠️ PHP CVEs. Update required!
I think RTS could continue to work if someone made a massive leap of faith and put all the modern infra around it that a AAA extraction s...
RFC: Pluggable SessionDB Provider — PostgreSQL, MySQL, and Beyond
v2.1.113+ broken on Termux/Android: native binary requires glibc, no JS fallback
I’m firmly anti-Tahoe and haven’t updated, and I’ve started to find Apple despicable.
[FEATURE] Link a source control repo as the source for organization skills
Feature Request: Option to disable paste text collapse in input field
We went down the WASM sandboxing rabbit hole at Gobii when building our agent infra.
Make CrashLoopBackoff timing tuneable, or add mechanism to exempt some exits
<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/). --> **Is this a BUG REPORT or FEATURE REQUEST?**: Feature request /kind feature **What happened**: As part of a development workflow, I intentionally killed a container in a pod with `restartPolicy: Always`. The plan was to do this repeatedly, as a quick way to restart the container and clear old state (and, in Minikube, to load image changes). The container went into a crash-loop backoff, making this anything but a quick option. **What you expected to happen**: I expected there so be some configuration allowing me to disable, or at least tune the timing of, the CrashLoopBackoff. **How to reproduce it (as minimally and precisely as possible)**: Create a pod with `restartPolicy: Always`, and intentionally exit a container repeatedly. **Anything else we need to know?**: I see that the backoff timing parameters are hard-coded constants here: https://github.com/kubernetes/kubernetes/blob/5f920426103085a28069a1ba3ec9b5301c19d075/pkg/kubelet/kubelet.go#L121 https://github.com/kubernetes/kubernetes/blob/5f920426103085a28069a1ba3ec9b5301c19d075/pkg/kubelet/kubelet.go#L155 One might reasonably expect these to be configurable at least at the kubelet level - say, by a setting like [these](https://github.co
Comments (0)
No comments yet. Start the discussion.