It matches all PVC objects that have the volume attributes class mentioned. 
  

                    "background": solved_result.background_tasks
                }
                # If status_code was set, use it, otherwise use the default from the
                # response class, in the case of redirect it's 307
                current_status_code = (
                    status_code if status_code else solved_result.response.status_code
                )
                if current_status_code is not None:

- Pods were not allowed to mix the usage of `user-namespaces` (`hostUsers: false`) and `volumeDevices`. Kubernetes returned an error in this case. ([#132868](https://github.com/kubernetes/kubernetes/pull/132868), [@rata](https://github.com/rata))

- Fix: consolidate logs for instance not found error (#105364, @nilo19) [SIG Cloud Provider]
- Fix: ignore not a VMSS error for VMAS nodes in EnsureBackendPoolDeleted. (#105404, @ialidzhikov) [SIG Cloud Provider]
- Fix: ignore the case when updating Azure tags (#104687, @nilo19) [SIG Cloud Provider]
- Revert PR #102925 which introduced unexpected scheduling behavior based on balanced resource allocation (#105239, @damemi) [SIG Scheduling]

* Nodecontroller doesn't flip readiness on pods if kubeletVersion < 1.2.0 ([#30828](https://github.com/kubernetes/kubernetes/pull/30828), [@bprashanth](https://github.com/bprashanth))
* AWS: Handle kube-down case where the LaunchConfig is dangling ([#30816](https://github.com/kubernetes/kubernetes/pull/30816), [@zmerlynn](https://github.com/zmerlynn))

* The init-container (pod.beta.kubernetes.io/init-containers) annotations used to accept capitalized field names that could be accidentally generated by the k8s.io/kubernetes/pkg/api package. Using an upper case field name will now return an error and all users should use the versioned API types from `pkg/api/v1` when serializing from Golang.

## Action Required Before Upgrading

* Important Security-related changes before upgrading

- Previously, the scheduling queue didn't notice any extenders' failures, potentially resulting in missed cluster events and Pods rejected by Extenders being stuck in the unschedulable pod pool for up to 5 minutes in the worst-case scenario. Now, the scheduling queue notices extenders' failures and requeues Pods rejected by Extenders appropriately.
   ([#122022](https://github.com/kubernetes/kubernetes/pull/122022), [@sanposhiho](https://github.com/sanposhiho))

l/11526.\n    opacity: 1;\n  }\n\n  // Disabled inputs\n  //\n  // HTML5 says that controls under a fieldset > legend:first-child won't be\n  // disabled if the fieldset is disabled. Due to implementation difficulty, we\n  // don't honor that edge case; we style them as disabled anyway.\n  &:disabled {\n    color: $input-disabled-color;\n    background-color: $input-disabled-bg;\n    border-color: $input-disabled-border-color;\n    // iOS fix for unreadable disabled content; see https://github.c...

* kubeadm: clean up exited containers and network checkpoints ([#43836](https://github.com/kubernetes/kubernetes/pull/43836), [@yujuhong](https://github.com/yujuhong))
* Fix corner-case with OnlyLocal Service healthchecks. ([#44313](https://github.com/kubernetes/kubernetes/pull/44313), [@thockin](https://github.com/thockin))

AA,IACA,QAAA,IAAA,IACA,SAAA,SACA,MAAA,IACA,IAAA,IAGF,YACE,iBAAA,YACA,kBAAA,EAGF,qBACE,mBAAA,EADF,yCAII,YAAA,EpFo+XJ,YoFh+XA,qBAEE,WAAA,KpFm+XF,yBoFh+XA,kCAGI,iBAAA,QACA,aAAA,QAJJ,6DASM,MAAA,qBATN,oDASM,MAAA,qBATN,wDASM,MAAA,qBATN,yDASM,MAAA,qBATN,+CASM,MAAA,qBATN,kEAaM,MAAA,qBAbN,wCpF8/XA,wEoF3+XQ,iBAAA,QACA,aAAA,kBACA,MAAA,QpFg/XR,0BoF1+XA,mCAGI,iBAAA,QACA,aAAA,QAJJ,8DASM,MAAA,eATN,qDASM,MAAA,eATN,yDASM,MAAA,eATN,0DASM,MAAA,eATN,gDASM,MAAA,eATN,mEAaM,MAAA,eAbN,yCpFwgYA,yEoFr/XQ,iBAAA,QACA,aAAA,...