for more details.) ([#129653](https://github.com/kubernetes/kubernetes/pull/129653), [@danwinship](https://github.com/danwinship)) [SIG Network]
- Updated `/version` response to report binary version information separate from compatibility version ([#130019](https://github.com/kubernetes/kubernetes/pull/130019), [@yongruilin](https://github.com/yongruilin)) [SIG API Machinery, Architecture, Release and Testing]

    - `kubectl create clusterrolebinding anonymous-access-review --clusterrole=system:basic-user --group=system:unauthenticated`
  - The deprecated --storage-versions flag has been removed. The storage versions will always be the default value built-in the kube-apiserver binary. ([#67678](https://github.com/kubernetes/kubernetes/pull/67678), [@caesarxuchao](https://github.com/caesarxuchao))

[okio_3_16_2]: https://square.github.io/okio/changelog/#version-3162
[okio_3_16_3]: https://square.github.io/okio/changelog/#version-3163
[okio_3_16_4]: https://square.github.io/okio/changelog/#version-3164
[okio_3_1_0]: https://square.github.io/okio/changelog/#version-310
[okio_3_2_0]: https://square.github.io/okio/changelog/#version-320
[okio_3_7_0]: https://square.github.io/okio/changelog/#version-370

## Action Required

- etcd2 as a backend is deprecated and support will be removed in Kubernetes 1.13.

- Kubeadm: upgrade supports fallback to the nearest known etcd version if an unknown k8s version is passed ([#88373](https://github.com/kubernetes/kubernetes/pull/88373), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle]

where BUILTIN\Users may be able to read container logs and NT
AUTHORITY\Authenticated Users may be able to modify container logs.

**Affected Versions**:
  - kubelet <= 1.27.15
  - kubelet <= 1.28.11
  - kubelet <= 1.29.6
  - kubelet <= 1.30.2 

**Fixed Versions**:
  - kubelet 1.27.16
  - kubelet 1.28.12
  - kubelet 1.29.7
  - kubelet 1.30.3 

labels.regularName=常規名稱
labels.replacement=替換
labels.sessionId=會話ID
labels.sortOrder=排序順序
labels.updatedBy=更新者
labels.updatedTime=更新時間
labels.urls=URL
labels.userAgent=使用者代理
labels.username=使用者名稱
labels.value=值
labels.versionNo=版本號
labels.cronExpression=排程
labels.dayForCleanup=刪除指定日期之前的文檔
labels.crawlingThreadCount=同時爬網數
labels.boost=提升值
labels.crawlingConfigName=名稱
labels.crawlingConfigPath=要爬網的路徑
labels.processType=處理類型

 *       wait();
 *     }
 *     value = newValue;
 *     notifyAll();
 *   }
 * }
 * }
 *
 * <h3>{@code ReentrantLock}</h3>
 *
 * <p>This version is much more verbose than the {@code synchronized} version, and still suffers
 * from the need for the programmer to remember to use {@code while} instead of {@code if}. However,

* 使用會替你執行容器映像的雲端服務等

### 套件需求 { #package-requirements }

你的應用通常會把「套件需求」放在某個檔案中。

這主要取決於你用什麼工具來安裝那些需求。

最常見的方式是準備一個 `requirements.txt` 檔案，逐行列出套件名稱與版本。

當然，你會用與在 [關於 FastAPI 版本](versions.md) 中讀到的相同概念，來設定版本範圍。

例如，你的 `requirements.txt` 可能像這樣：

```
fastapi[standard]>=0.113.0,<0.114.0
pydantic>=2.7.0,<3.0.0
```

接著你通常會用 `pip` 來安裝這些套件相依，例如：

<div class="termy">

- Enhanced the Dynamic Resource Allocation (DRA) with an updated version of the resource.k8s.io API group. The primary user-facing type remains the ResourceClaim, however significant changes have been made, resulting in the new version, v1alpha3, which is not compatible with the previous version. ([#125488](https://github.com/kubernetes/kubernetes/pull/125488), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth,...