#### kube-scheduler:
- A kubescheduler.config.k8s.io/v1alpha2 configuration file version is now accepted, with support for multiple scheduling profiles ([#87628](https://github.com/kubernetes/kubernetes/pull/87628), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling]

  - [beta] AppArmor profiles can be specified & applied to pod containers ([docs](http://kubernetes.io/docs/admin/apparmor/)) ([kubernetes/features#24](https://github.com/kubernetes/enhancements/issues/24))

* Fix kube vsphere.kerneltime ([#34997](https://github.com/kubernetes/kubernetes/pull/34997), [@kerneltime](https://github.com/kerneltime))
* Add PSP support for seccomp profiles ([#28300](https://github.com/kubernetes/kubernetes/pull/28300), [@pweil-](https://github.com/pweil-))
* Updated Go to 1.7 ([#28742](https://github.com/kubernetes/kubernetes/pull/28742), [@jessfraz](https://github.com/jessfraz))

- Allowed `ImageVolume` for Restricted PSA profiles. ([#130394](https://github.com/kubernetes/kubernetes/pull/130394), [@Barakmor1](https://github.com/Barakmor1))

- `AppArmor` profiles specified in the Pod or container `SecurityContext` were no longer copied to deprecated `AppArmor` annotations (prefix `container.apparmor.security.beta.kubernetes.io/`). Anything that inspected the deprecated annotations must be migrated to use...

- Users can traverse all the pods that are in the scheduler and waiting in the permit stage through method `IterateOverWaitingPods`. In other words,  all waitingPods in scheduler can be obtained from any profiles. Before this commit, each profile could only obtain waitingPods within that profile. ([#124926](https://github.com/kubernetes/kubernetes/pull/124926), [@kerthcet](https://github.com/kerthcet)) [SIG Scheduling]

* kubectl has gained new --profile and --profile-output options to output go profiles ([#68681](https://github.com/kubernetes/kubernetes/pull/68681), [@dlespiau](https://github.com/dlespiau))

- Record requests rejected with 429 in the apiserver_request_total metric ([#108927](https://github.com/kubernetes/kubernetes/pull/108927), [@wojtek-t](https://github.com/wojtek-t))
- Removed validation if AppArmor profiles are loaded on the local node. This should be handled by the container runtime. ([#97966](https://github.com/kubernetes/kubernetes/pull/97966), [@saschagrunert](https://github.com/saschagrunert))

{ panic("ecdsa: reseed interval exceeded") } tlen := 0 for tlen < len(out) { // V = HMAC_K(V) // T = T || V d.hK.Reset() d.hK.Write(d.V) d.V = d.hK.Sum(d.V[:0]) tlen += copy(out[tlen:], d.V) } // Note that if this function shows up on ECDSA-level profiles, this can be // optimized in the common case by deferring the rest to the next Generate // call, which will never come in nearly all cases. // HMAC_DRBG_Update, per Section 10.1.2.2, without provided_data. // K = HMAC (K, V || 0x00) d.hK.Reset()...

pkg runtime/debug, func PrintStack()
pkg runtime/debug, func Stack() []uint8
pkg runtime/pprof, func Lookup(string) *Profile
pkg runtime/pprof, func NewProfile(string) *Profile
pkg runtime/pprof, func Profiles() []*Profile
pkg runtime/pprof, func StartCPUProfile(io.Writer) error
pkg runtime/pprof, func StopCPUProfile()
pkg runtime/pprof, func WriteHeapProfile(io.Writer) error