http://example.com/(%28:%3A%29)  s:http h:example.com p:/(%28:%3A%29)
http://example.com/%3A%3a%3C%3c  s:http h:example.com p:/%3A%3a%3C%3c
http://example.com/foo\tbar  s:http h:example.com p:/foobar
http://example.com\\\\foo\\\\bar  s:http h:example.com p://foo//bar
http://example.com/%7Ffp3%3Eju%3Dduvgw%3Dd  s:http h:example.com p:/%7Ffp3%3Eju%3Dduvgw%3Dd
http://example.com/@asdf%40  s:http h:example.com p:/@asdf%40

    assertThat(socketAddress.socketHost).isEqualTo("127.0.0.1")
    socketAddress =
      InetSocketAddress(
        InetAddress.getByAddress("foobar", byteArrayOf(127, 0, 0, 1)),
        1234,
      )
    assertThat(socketAddress.socketHost).isEqualTo("127.0.0.1")
  }

  @Test fun routeToString() {
    val ipv4Address =
      InetAddress.getByAddress(

You can continue to use the alpha version of this feature (with one caveat -- see below), in which you specify affinity requests using Pod annotations, in 1.6 by including `AffinityInAnnotations=true` in `--feature-gates`, such as `--feature-gates=FooBar=true,AffinityInAnnotations=true`. Otherwise, you must modify your PodSpecs that currently use the `scheduler.alpha.kubernetes.io/affinity` annotation on Pod, to instead use the `affinity` field in the PodSpec. Support for the annotation will be removed...