Chaoren Lin <******@****.***> 1700246690 -0800

Tim Hockin <******@****.***> 1629416503 -0700

Shinsuke Sugaya <******@****.***> 1715236287 +0900

Emre Sülün <******@****.***> 1646040883 +0300

SAM Conversions
---------------

When you use Java APIs from Kotlin you can operate on Java interfaces as if they were Kotlin
lambdas. The [feature][java_sams] is available for interfaces that define a Single Abstract Method
(SAM).

But when you use Kotlin APIs from Kotlin there’s no automatic conversion. Code that used SAM lambdas
with OkHttp 3.x: must use `object :` with OkHttp 4.x:

   *       the same.
   *   <li>The unreserved characters ".", "-", "~", and "_" remain the same.
   *   <li>The general delimiters "@" and ":" remain the same.
   *   <li>The subdelimiters "!", "$", "&amp;", "'", "(", ")", "*", "+", ",", ";", and "=" remain
   *       the same.
   *   <li>The space character " " is converted into %20.

        OutputStream jsonOutput = SearchEngineUtil.getXContentBuilderOutputStream(callback, XContentType.JSON);
        assertNotNull(jsonOutput);

        // Test with YAML
        OutputStream yamlOutput = SearchEngineUtil.getXContentBuilderOutputStream(callback, XContentType.YAML);
        assertNotNull(yamlOutput);
    }

    public void test_getXContentOutputStream_success() {
        ToXContent xContent = new ToXContent() {

        CharMappingItem item4 = new CharMappingItem(4L, inputs1, "different");

        // Same inputs and output should have same hash code
        assertEquals(item1.hashCode(), item2.hashCode());

        // Different inputs should have different hash code
        assertNotSame(item1.hashCode(), item3.hashCode());

        // Same inputs but different output should have different hash code

* Fix hyperkube flag parsing ([#25512](https://github.com/kubernetes/kubernetes/pull/25512), [@colhom](https://github.com/colhom))
* kubectl rolling-update support for same image ([#24645](https://github.com/kubernetes/kubernetes/pull/24645), [@jlowdermilk](https://github.com/jlowdermilk))

**How can I mitigate this prior to installing 1.5.5?**

1. Export existing PodSecurityPolicy objects:
  * `kubectl get podsecuritypolicies -o yaml > psp.yaml`
2. Review and delete any PodSecurityPolicy objects you do not want all pod-creating users to be able to use (NOTE: Privileged users that were making use of those policies will also lose access to those policies). For example: