* Specifically the new controller watches the API server for scheduled pods. It processes each pod and ensures that any volumes that implement the volume Attacher interface are attached to the node their pod is scheduled to.

                      .build(),
                  )
                val response = call.execute()
                assertThat(response.body.string()).isEqualTo("ABC")
                // Wait until the GOAWAY has been processed.
                val connection = chain.connection() as RealConnection?
                while (connection!!.isHealthy(false));
              }
              return chain.proceed(chain.request())
            }

- Updating kubelet permissions check for Windows nodes to see if process is elevated instead of checking if process owner is in Administrators group ([#111078](https://github.com/kubernetes/kubernetes/pull/111078), [@marosset](https://github.com/marosset)) [SIG Node and Windows]

## Dependencies

### Added

    </magic>
  </mime-type>
  <mime-type type="application/x-hwp-v5">
    <_comment>Hangul Word Processor File v5</_comment>
    <sub-class-of type="application/x-tika-msoffice"/>
  </mime-type>
  <mime-type type="application/hwp+zip">
    <_comment>Hangul Word Processor File, zip based</_comment>
    <sub-class-of type="application/zip"/>
    <glob pattern="*.hwpx"/>
  </mime-type>

*...

    enableProtocol(Protocol.HTTP_2)
    canceledBeforeResponseReadSignalsOnFailure()
  }

  /**
   * There's a race condition where the cancel may apply after the stream has already been
   * processed.
   */
  @Test
  fun canceledAfterResponseIsDeliveredBreaksStreamButSignalsOnce() {
    server.enqueue(MockResponse(body = "A"))
    val latch = CountDownLatch(1)
    val bodyRef = AtomicReference<String?>()

- Added support for a new kubectl output format, `kyaml`. KYAML was a strict subset of YAML and should be accepted by any YAML processor. The formatting of KYAML was halfway between JSON and YAML.  Because it was more explicit than the default YAML style, it was less error-prone. ([#132942](https://github.com/kubernetes/kubernetes/pull/132942), [@thockin](https://github.com/thockin))...

- GCE/Windows: When the service cannot be stopped Stackdriver logging processes are now force killed ([#77378](https://github.com/kubernetes/kubernetes/pull/77378), [@yujuhong](https://github.com/yujuhong))

    * Each deployment method should bind users/groups to the ClusterRoles if they are using this feature.
* Adds AllowPrivilegeEscalation to control whether a process can gain more privileges than its parent process ([#47019](https://github.com/kubernetes/kubernetes/pull/47019), [@jessfraz](https://github.com/jessfraz))

* Fix an issue in inter-pod affinity predicate that cause affinity to self being processed correctly ([#62591](https://github.com/kubernetes/kubernetes/pull/62591), [@bsalamat](https://github.com/bsalamat))