- Fix a bug that when PodTopologySpread rejects Pods, they may be stuck in Pending state for 5 min in a worst case scenario.
  The same problem could happen with custom plugins which have Pod/Add or Pod/Update in EventsToRegister,

* changes timeout value in csi plugin from 15s to 2min which fixes the timeout issue ([#79529](https://github.com/kubernetes/kubernetes/pull/79529), [@andyzhangx](https://github.com/andyzhangx))



# v1.13.9

[Documentation](https://docs.k8s.io)

- Scheduler's assumed pods have 2min instead of 30s to receive nodeName pod updates ([#106686](https://github.com/kubernetes/kubernetes/pull/106686), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling]

## Dependencies

### Added
_Nothing has changed._

  After the connection closed(received GOAWAY), the client's other in-flight requests won't be affected, and the client will reconnect. 
  The flag min value is 0 (off), max is .02 (1/50 requests); .001 (1/1000) is a recommended starting point.

pkg syscall (linux-386), const VERASE ideal-int
pkg syscall (linux-386), const VINTR ideal-int
pkg syscall (linux-386), const VKILL ideal-int
pkg syscall (linux-386), const VLNEXT ideal-int
pkg syscall (linux-386), const VMIN ideal-int
pkg syscall (linux-386), const VQUIT ideal-int
pkg syscall (linux-386), const VREPRINT ideal-int
pkg syscall (linux-386), const VSTART ideal-int
pkg syscall (linux-386), const VSTOP ideal-int

subtle import "crypto/internal/fips140/alias" // XORBytes sets dst[i] = x[i] ^ y[i] for all i < n = min(len(x), len(y)), // returning n, the number of bytes written to dst. // // If dst does not have length at least n, // XORBytes panics without writing anything to dst. // // dst and x or y may overlap exactly or not at all, // otherwise XORBytes may panic. func XORBytes(dst, x, y []byte) int { n := min(len(x), len(y)) if n == 0 { return 0 } if n > len(dst) { panic("subtle.XORBytes: dst too short")...