Before upgrading to Kubernetes 1.11, you must keep the following in mind:

    </magic>
  </mime-type>
  <mime-type type="application/x-x509-key;format=der">
    <sub-class-of type="application/x-x509-key"/>
    <!-- These are just a bunch of magic integers as defined by the key format... -->
    <!-- Always seem to have a version integer as their first entry, -->
    <!--  normally 00, 01 or 02, check for that -->
    <magic priority="40">

   * ordering of writes to a segment is sequentially consistent. An update to the map and recording
   * of reads may not be immediately reflected on the algorithm's data structures. These structures
   * are guarded by a lock and operations are applied in batches to avoid lock contention. The
   * penalty of applying the batches is spread across threads so that the amortized cost is slightly

### Other (Cleanup or Flake)

   * Old implementations of OkHttp's response cache wrote header fields like ":status: 200 OK". This
   * broke our cached response parser because it split on the first colon. This regression test
   * exists to help us read these old bad cache entries.
   *
   * https://github.com/square/okhttp/issues/227
   */
  @Test
  fun testGoldenCacheResponse() {
    cache.close()
    server.enqueue(
      MockResponse

  @Test
  fun writeTimeouts() {
    val server = MockWebServer()
    // Sockets on some platforms can have large buffers that mean writes do not block when
    // required. These socket factories explicitly set the buffer sizes on sockets created.
    val socketBufferSize = 4 * 1024
    server.serverSocketFactory =
      object : DelegatingServerSocketFactory(getDefault()) {

          "type": "stop",
          "stopwords": ["a", "an", "and", "are", "as", "at", "be", "but", "by", "for", "if", "in", "into", "is", "it", "no", "not", "of", "on", "or", "such", "that", "the", "their", "then", "there", "these", "they", "this", "to", "was", "will", "with"]
        },
        "arabic_stop": {
          "type":       "stop",

          "type": "stop",
          "stopwords": ["a", "an", "and", "are", "as", "at", "be", "but", "by", "for", "if", "in", "into", "is", "it", "no", "not", "of", "on", "or", "such", "that", "the", "their", "then", "there", "these", "they", "this", "to", "was", "will", "with"]
        },
        "arabic_stop": {
          "type":       "stop",

    assertThat(server.takeRequest().exchangeIndex).isEqualTo(2)
  }

  /**
   * Each OkHttpClient used to get its own instance of NullProxySelector, and because these weren't
   * equal their connections weren't pooled. That's a nasty performance bug!
   *
   * https://github.com/square/okhttp/issues/5519
   */
  @Test
  fun connectionPoolingWithFreshClientSamePool() {

- The kube-scheduler added scheduling hints for the InterPodAffinity plugin.
  These hints allow the scheduler to retry scheduling a Pod