- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for aquele (0.18 sec)
-
CHANGELOG/CHANGELOG-1.28.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 20:44:48 GMT 2024 - 385.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.8.md
* Webhook always retries connection reset error. ([#53947](https://github.com/kubernetes/kubernetes/pull/53947), [@crassirostris](https://github.com/crassirostris)) * Adjust batching audit webhook default parameters: increase queue size, batch size, and initial backoff. Add throttling to the batching audit webhook. Default rate limit is 10 QPS. ([#53417](https://github.com/kubernetes/kubernetes/pull/53417), [@crassirostris](https://github.com/crassirostris))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Feb 20 15:45:02 GMT 2024 - 312.2K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.23.md
- Added a `Processing` condition for the `workqueue` API. Changed `Shutdown` for the `workqueue` API to wait until the work queue finishes processing all in-flight items. ([#101928](https://github.com/kubernetes/kubernetes/pull/101928), [@alexanderConstantinescu](https://github.com/alexanderConstantinescu))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Feb 28 21:06:52 GMT 2023 - 424.5K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.25.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Nov 16 11:30:31 GMT 2023 - 419K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.24.md
- Add a deprecated cmd flag for the time interval between flushing pods from unschedulable queue to active queue or backoff queue. ([#108017](https://github.com/kubernetes/kubernetes/pull/108017), [@denkensk](https://github.com/denkensk))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Aug 24 00:02:43 GMT 2023 - 473.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.30.md
- Previously, the scheduling queue didn't notice any extenders' failures, potentially resulting in missed cluster events and Pods rejected by Extenders being stuck in the unschedulable pod pool for up to 5 minutes in the worst-case scenario. Now, the scheduling queue notices extenders' failures and requeues Pods rejected by Extenders appropriately.
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Wed Apr 17 17:56:15 GMT 2024 - 227.9K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.29.md
Fixed a situation when, sometimes, the scheduler incorrectly placed a pod in the `unschedulable` queue instead of the `backoff` queue. This happened when some plugin previously declared the pod as `unschedulable` and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the `active` queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 21:41:06 GMT 2024 - 299.9K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.26.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Mar 14 16:24:51 GMT 2024 - 425.7K bytes - Viewed (0)