String INDEX_DOCUMENT_CRAWLER_INDEX = "index.document.crawler.index";

    /** The key of the configuration. e.g. 10 */
    String INDEX_DOCUMENT_CRAWLER_QUEUE_number_of_shards = "index.document.crawler.queue.number_of_shards";

    /** The key of the configuration. e.g. 10 */
    String INDEX_DOCUMENT_CRAWLER_DATA_number_of_shards = "index.document.crawler.data.number_of_shards";

- The scheduling queue didn't notice any extenders' failures, it could miss some cluster events,
  and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario.

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))...

- The scheduling queue didn't notice any extenders' failures, it could miss some cluster events,
  and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario.

* Add validation for CustomResources via JSON Schema. ([#47263](https://github.com/kubernetes/kubernetes/pull/47263), [@nikhita](https://github.com/nikhita))
* enqueue a sync task to wake up jobcontroller to check job ActiveDeadlineSeconds in time ([#48454](https://github.com/kubernetes/kubernetes/pull/48454), [@weiwei04](https://github.com/weiwei04))

- 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))

pkg syscall (darwin-arm64), const SYS_KEVENT64 ideal-int
pkg syscall (darwin-arm64), const SYS_KILL = 37
pkg syscall (darwin-arm64), const SYS_KILL ideal-int
pkg syscall (darwin-arm64), const SYS_KQUEUE = 362
pkg syscall (darwin-arm64), const SYS_KQUEUE ideal-int
pkg syscall (darwin-arm64), const SYS_LCHOWN = 364
pkg syscall (darwin-arm64), const SYS_LCHOWN ideal-int
pkg syscall (darwin-arm64), const SYS_LEDGER = 373

pkg syscall (netbsd-arm64-cgo), const SYS_KQUEUE1 = 455
pkg syscall (netbsd-arm64-cgo), const SYS_KQUEUE1 ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_KQUEUE = 344
pkg syscall (netbsd-arm64-cgo), const SYS_KQUEUE ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_KTRACE = 45
pkg syscall (netbsd-arm64-cgo), const SYS_KTRACE ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_LCHFLAGS = 304

- 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))...

- Implement the scheduling framework with `Reserve`, `Prebind`, `Permit`, `Post-bind`, `Queue sort` and `Unreserve` extension points.
([#77567](https://github.com/kubernetes/kubernetes/pull/77567), [@wgliang](https://github.com/wgliang))