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

for this to panic: labels are fixed strings, // and context is either a fixed-length computed hash, or parsed from a // field which has the same length limitation. // // Another reasonable approach might be to return a randomized slice if // we encounter an error, which would break the connection, but avoid // panicking. This would perhaps be safer but significantly more // confusing to users. panic("tls13: label or context too long") } hkdfLabel := make([]byte, 0, 2+1+len("tls13 ")+len(label)+1+len(context))...