### (No, really, you MUST read this before you upgrade)

- The StreamingProxyRedirects feature and `--redirect-container-streaming` flag are deprecated, and will be removed in a future release. The default behavior (proxy streaming requests through the kubelet) will be the only supported option.

#### Cluster Selection
* [alpha] Federation [ClusterSelector annotation](https://kubernetes.io/docs/tasks/administer-federation/cluster/#clusterselector-annotation) to direct objects to federated clusters with matching labels.


### **Instrumentation**
#### Core Metrics API

            Arrays.fill(sessionKey, (byte) 0xEE);

            Smb2SigningDigest digest = new Smb2SigningDigest(sessionKey, Smb2Constants.SMB2_DIALECT_0202, null);

            // Close multiple times should not throw
            digest.close();
            digest.close();
            digest.secureWipeKey();
            digest.close();

            // Operations should still fail
            byte[] data = new byte[128];

    * Logging Agent Improvements
    * Bump logging agent version to 0.2-1.5.33-1-k8s-1.
    * Appropriately set log severity for k8s_container.
    * Fix detect exceptions plugin to analyze message field instead of log field.
    * Fix detect exceptions plugin to analyze streams based on local resource id.
    * Disable the metadata agent for monitored resource construction in logging.

d.Write(padlen) if d.nx != 0 { panic("d.nx != 0") } var digest [size]byte byteorder.BEPutUint32(digest[0:], d.h[0]) byteorder.BEPutUint32(digest[4:], d.h[1]) byteorder.BEPutUint32(digest[8:], d.h[2]) byteorder.BEPutUint32(digest[12:], d.h[3]) byteorder.BEPutUint32(digest[16:], d.h[4]) byteorder.BEPutUint32(digest[20:], d.h[5]) byteorder.BEPutUint32(digest[24:], d.h[6]) if !d.is224 { byteorder.BEPutUint32(digest[28:], d.h[7]) } return digest } golang.org/fips140@v1.0.0-c2097c7c/fips140/v1.0.0-c20...

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

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

# 直接回傳 Response { #return-a-response-directly }

當你建立一個 **FastAPI** 的路徑操作 (path operation) 時，通常可以從中回傳任何資料：`dict`、`list`、Pydantic 模型、資料庫模型等。

如果你宣告了 [回應模型](../tutorial/response-model.md)，FastAPI 會用 Pydantic 將資料序列化為 JSON。

如果你沒有宣告回應模型，FastAPI 會使用在[JSON 相容編碼器](../tutorial/encoder.md)中說明的 `jsonable_encoder`，並把它放進 `JSONResponse`。

但你也可以直接從路徑操作回傳 `JSONResponse`。

/// tip

     * Test validation of excessive negotiate context count.
     */
    @Test
    public void testExcessiveNegotiateContextCount() {
        byte[] buffer = createBasicNegotiateResponseBuffer();
        // Set SMB 3.1.1 dialect
        SMBUtil.writeInt2(0x0311, buffer, 4);
        // Set excessive negotiate context count (should be limited to 100)
        SMBUtil.writeInt2(1000, buffer, 6);
        // Set negotiate context offset to valid value

# Возврат ответа напрямую { #return-a-response-directly }

Когда вы создаёте **FastAPI** *операцию пути*, вы можете возвращать из неё любые данные: `dict`, `list`, Pydantic-модель, модель базы данных и т.д.

Если вы объявите [Модель ответа](../tutorial/response-model.md), FastAPI будет использовать её для сериализации данных в JSON с помощью Pydantic.