Sonra alt uygulamanızı ve onun *path operation*’larını oluşturun.

Bu alt uygulama da standart bir FastAPI uygulamasıdır; ancak "mount" edilecek olan budur:

{* ../../docs_src/sub_applications/tutorial001_py310.py hl[11, 14:16] *}

### Alt uygulamayı mount edin { #mount-the-sub-application }

Üst seviye uygulamanızda (`app`), alt uygulama `subapi`’yi mount edin.

Bu örnekte `/subapi` path’ine mount edilecektir:

Then, create your sub-application, and its *path operations*.

This sub-application is just another standard FastAPI application, but this is the one that will be "mounted":

{* ../../docs_src/sub_applications/tutorial001_py310.py hl[11, 14:16] *}

### Mount the sub-application { #mount-the-sub-application }

In your top-level application, `app`, mount the sub-application, `subapi`.

In this case, it will be mounted at the path `/subapi`:

### 하위 애플리케이션 { #sub-application }

그 다음, 하위 애플리케이션과 그 *경로 처리*를 생성합니다.

이 하위 애플리케이션은 또 다른 표준 FastAPI 애플리케이션이지만, "마운트"될 애플리케이션입니다:

{* ../../docs_src/sub_applications/tutorial001_py310.py hl[11, 14:16] *}

### 하위 애플리케이션 마운트 { #mount-the-sub-application }

최상위 애플리케이션 `app`에서 하위 애플리케이션 `subapi`를 마운트합니다.

이 경우 `/subapi` 경로에 마운트됩니다:

{* ../../docs_src/sub_applications/tutorial001_py310.py hl[11, 19] *}

### 子應用程式 { #sub-application }

接著，建立你的子應用程式及其*路徑操作*。

這個子應用程式就是另一個標準的 FastAPI 應用，但這個會被「掛載」：

{* ../../docs_src/sub_applications/tutorial001_py310.py hl[11, 14:16] *}

### 掛載子應用程式 { #mount-the-sub-application }

在你的頂層應用程式 `app` 中，掛載子應用程式 `subapi`。

在此範例中，它會被掛載在路徑 `/subapi`：

{* ../../docs_src/sub_applications/tutorial001_py310.py hl[11, 19] *}

    testRotate(new char[] {'1', '2', '3', '4', '5'}, -3, new char[] {'4', '5', '1', '2', '3'});
    testRotate(new char[] {'1', '2', '3', '4', '5'}, -1, new char[] {'2', '3', '4', '5', '1'});
    testRotate(new char[] {'1', '2', '3', '4', '5'}, 0, new char[] {'1', '2', '3', '4', '5'});
    testRotate(new char[] {'1', '2', '3', '4', '5'}, 1, new char[] {'5', '1', '2', '3', '4'});

- NodeOutOfServiceVolumeDetach is now beta. ([#113511](https://github.com/kubernetes/kubernetes/pull/113511), [@xing-yang](https://github.com/xing-yang)) [SIG Node and Storage]
- Pod Security admission: the pod-security `warn` level will now default to the `enforce` level. ([#113491](https://github.com/kubernetes/kubernetes/pull/113491), [@tallclair](https://github.com/tallclair)) [SIG Auth and Security]

- Pods will now post their readiness during termination. ([#110418](https://github.com/kubernetes/kubernetes/pull/110418), [@aojea](https://github.com/aojea)) [SIG Network, Node and Testing]

            SrvCopychunk[] testCases = { new SrvCopychunk(1, 2, 3), new SrvCopychunk(4, 5, 6), new SrvCopychunk(7, 8, 9),
                    new SrvCopychunk(10, 11, 12), new SrvCopychunk(13, 14, 15) };

            for (int numChunks = 0; numChunks <= testCases.length; numChunks++) {
                // Create copy with varying number of chunks

- Kubelet: fix GetAllocatableCPUs method in cpumanager ([#113420](https://github.com/kubernetes/kubernetes/pull/113420), [@Garrybest](https://github.com/Garrybest)) [SIG Node]
- Pod logs using --timestamps are not broken up with timestamps anymore. ([#113515](https://github.com/kubernetes/kubernetes/pull/113515), [@rphillips](https://github.com/rphillips)) [SIG Node]

## Dependencies

### Added

- Kube-apiserver: Resolved an issue causing unnecessary warning log messages about enabled alpha APIs during API server startup....