- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 17 for cycle (0.15 sec)
-
CHANGELOG/CHANGELOG-1.13.md
* scheduler: use incremental scheduling cycle in PriorityQueue to put all in-flight unschedulable pods back to active queue if we received move request ([#73309](https://github.com/kubernetes/kubernetes/pull/73309), [@cofyc](https://github.com/cofyc))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu May 05 13:44:43 GMT 2022 - 273.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.27.md
eligible node(s) for pod with bound claim(s) to local `PersistentVolume(s)` ([#109877](https://github.com/kubernetes/kubernetes/pull/109877), [@yibozhuang](https://github.com/yibozhuang)) - Scheduling cycle now terminates immediately when any scheduler plugin returns an `unschedulableAndUnresolvable` status in `PostFilter`. ([#114699](https://github.com/kubernetes/kubernetes/pull/114699), [@kerthcet](https://github.com/kerthcet))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 15:20:21 GMT 2024 - 434.3K bytes - Viewed (3) -
CHANGELOG/CHANGELOG-1.12.md
* scheduler: use incremental scheduling cycle in PriorityQueue to put all in-flight unschedulable pods back to active queue if we received move request ([#73309](https://github.com/kubernetes/kubernetes/pull/73309), [@cofyc](https://github.com/cofyc))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Feb 06 06:04:15 GMT 2020 - 293.8K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.11.md
### SIG Auth Work this cycle focused on graduating existing functions, and on making security functions more understandable for users.
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Feb 06 06:04:15 GMT 2020 - 328.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.18.md
- Scheduler framework permit plugins now run at the end of the scheduling cycle, after reserve plugins. Waiting on permit will remain in the beginning of the binding cycle. ([#88199](https://github.com/kubernetes/kubernetes/pull/88199), [@mateuszlitwin](https://github.com/mateuszlitwin)) [SIG Scheduling]
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Wed Jun 16 17:18:28 GMT 2021 - 373.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.9.md
### Instrumentation
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Nov 16 10:46:27 GMT 2021 - 313.7K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.21.md
- When using `kubectl replace` (or the equivalent API call) on a Service, the caller no longer needs to do a read-modify-write cycle to fetch the allocated values for `.spec.clusterIP` and `.spec.ports[].nodePort`. Instead the API server will automatically carry these forward from the original object when the new object does not specify them. ([#104673](https://github.com/kube...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Fri Oct 14 07:03:14 GMT 2022 - 367.3K bytes - Viewed (4) -
CHANGELOG/CHANGELOG-1.8.md
* request a client certificate from the API server during the boot cycle and pause * waiting for the request to be satisfied. It will continually refresh the certificate * as the certificates expiration approaches.
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.28.md
When the scheduling queue receives a cluster event, before moving each Pod from unschedulable pod pool to activeQ/backoffQ, it will call QueueingHintFn of plugins that rejected each Pod in the previous scheduling cycle. Depending on the value returned from QueueingHintFn, the scheduling queue changes how it queues each Pod: - if more than one QueueingHintFn returns QueueImmediately, it queues Pod to activeQ.
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.22.md
- When using `kubectl replace` (or the equivalent API call) on a Service, the caller no longer needs to do a read-modify-write cycle to fetch the allocated values for `.spec.clusterIP` and `.spec.ports[].nodePort`. Instead the API server will automatically carry these forward from the original object when the new object does not specify them. ([#104672](https://github.com/kube...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Dec 13 12:43:45 GMT 2022 - 454.1K bytes - Viewed (1)