The API Server will no longer proxy non-101 responses for upgrade requests. This could break proxied backends (such as an extension API server) that respond to upgrade requests with a non-101 response code. ([#92941](https://github.com/kubernetes/kubernetes/pull/92941), [@tallclair](https://github.com/tallclair)) [SIG API Machinery]
 
## Changes by Kind

In diesen Fällen können Sie einen `Response`-Parameter verwenden.

## Einen `Response`-Parameter verwenden

Sie können einen Parameter vom Typ `Response` in Ihrer *Pfadoperation-Funktion* deklarieren (wie Sie es auch für Cookies und Header tun können).

Anschließend können Sie den `status_code` in diesem *vorübergehenden* Response-Objekt festlegen.

При этом вы всё ещё хотите иметь возможность фильтровать и преобразовывать возвращаемые данные с помощью `response_model`.

Для таких случаев вы можете использовать параметр `Response`.

## Использование параметра `Response`

Вы можете объявить параметр типа `Response` в вашей *функции обработки пути* (так же как для cookies и headers).

И затем вы можете установить `status_code` в этом *временном* объекте ответа.

     * @param <Response> the response type
     * @param action     the action to execute
     * @param request    the action request
     * @return a future for the action response
     */
    @Override
    public <Request extends ActionRequest, Response extends ActionResponse> ActionFuture<Response> execute(
            final ActionType<Response> action, final Request request) {

  The API Server will no longer proxy non-101 responses for upgrade requests. This could break proxied backends (such as an extension API server) that respond to upgrade requests with a non-101 response code. ([#92941](https://github.com/kubernetes/kubernetes/pull/92941), [@tallclair](https://github.com/tallclair)) [SIG API Machinery]
 
## Changes by Kind

- Resolves a spurious "Unknown discovery response content-type" error in client-go discovery requests by tolerating extra content-type parameters in API responses ([#117571](https://github.com/kubernetes/kubernetes/pull/117571), [@seans3](https://github.com/seans3)) [SIG API Machinery]

- Resolves a spurious "Unknown discovery response content-type" error in client-go discovery requests by tolerating extra content-type parameters in API responses ([#117637](https://github.com/kubernetes/kubernetes/pull/117637), [@seans3](https://github.com/seans3)) [SIG API Machinery]

        assertEquals(statusCode, response.getHttpStatusCode());
    }

    @Test
    public void testEncoding() {
        CurlResponse response = new CurlResponse();
        String encoding = "UTF-8";

        response.setEncoding(encoding);

        assertEquals(encoding, response.getEncoding());
    }

    @Test
    public void testContentException() {

        response = new Trans2QueryFSInformationResponse(config, informationLevel);

        assertNotNull(response);
        assertEquals(informationLevel, response.getInformationLevel());
        assertEquals(ServerMessageBlock.SMB_COM_TRANSACTION2, response.getCommand());
        assertEquals(SmbComTransaction.TRANS2_QUERY_FS_INFORMATION, response.getSubCommand());
    }

    @Test

        setTreeIdMethod.setAccessible(true);
        setTreeIdMethod.invoke(response, -1);
        assertFalse(response.isValidTid());

        // Test valid TID
        setTreeIdMethod.invoke(response, 100);
        assertTrue(response.isValidTid());

        // Test zero TID (valid)
        setTreeIdMethod.invoke(response, 0);
        assertTrue(response.isValidTid());
    }

    @Test