oh?uoh??t&a&d?ts&e!laer??lla???is!.&a&mgif,vnac.ym,?bewwuoj,derauqspw,e&lej,ni&effac,lnigol,?r&auqs,ocevon,?winmo,?l&aicosnepo,enapc,?n&eyb,o&iton,yc,??s&ihtedam,pvtsaf,?thrs,w&eiverp,olfyeh,?xevnoc,ysrab,?bew!.remarf,??ov?ra?t&ioled?ol??utitsni??u&lb?qi&nilc?tuob???v!.&21e?b&ew?ib?og??ce&r?t??e&dnerpme?rots??gro?lim?m&o&c?n??rif??o&c?fni??rar?stra?t&en?ni??ude?vog??as?e3gerb2h--nx?i&l!.&mea,xlh,??rd?ssergorp??ol??w&kct--nx?r??xul?y!.&gro?lim?moc?ten?ude?vog????f&0f3rkcg--nx?198xim--nx?280xim--n...

* Scale kube-proxy conntrack limits by cores (new default behavior) ([#28876](https://github.com/kubernetes/kubernetes/pull/28876), [@thockin](https://github.com/thockin))
* Don't recreate lb cloud resources on kcm restart ([#29082](https://github.com/kubernetes/kubernetes/pull/29082), [@bprashanth](https://github.com/bprashanth))

## Known Issues