- Fixes a problem with 63-second or 1-second connection delays with some VXLAN-based
  network plugins which was first widely noticed in 1.16 (though some users saw it
  earlier than that, possibly only with specific network plugins). If you were previously

#### Dizin Yapısı { #directory-structure }

Artık dizin yapınız şöyle olmalı:

```
.
├── app
│   ├── __init__.py
│   └── main.py
├── Dockerfile

#### Estructura de Directorios { #directory-structure }

Ahora deberías tener una estructura de directorios como:

```
.
├── app
│   ├── __init__.py
│   └── main.py

#### Verzeichnisstruktur { #directory-structure }

Sie sollten jetzt eine Verzeichnisstruktur wie diese haben:

```
.
├── app
│   ├── __init__.py
│   └── main.py

#### Структура директорій { #directory-structure }

Зараз у вас має бути така структура директорій:

```
.
├── app
│   ├── __init__.py
│   └── main.py
├── Dockerfile

    public static final String LABELS_search_result_status_over = "{labels.search_result_status_over}";

    /** The key of the message: ({0} seconds) */
    public static final String LABELS_search_result_time = "{labels.search_result_time}";

    /** The key of the message: Prev */
    public static final String LABELS_prev_page = "{labels.prev_page}";

在使用 `docker compose` 时这一点尤为明显。更多技术细节参见该 FAQ：[为什么我的服务需要 10 秒才能重新创建或停止？](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop)

#### 目录结构 { #directory-structure }

此时你的目录结构应类似：

```
.
├── app
│   ├── __init__.py
│   └── main.py
├── Dockerfile
└── requirements.txt
```

#### Estrutura de diretórios { #directory-structure }

Agora você deve haver uma estrutura de diretório como:

```
.
├── app
│   ├── __init__.py
│   └── main.py

- `PodLifecycleSleepAction` is now turned on by default allowing users to create containers with sleep lifecycle action with a duration of zero seconds ([#130621](https://github.com/kubernetes/kubernetes/pull/130621), [@sreeram-venkitesh](https://github.com/sreeram-venkitesh)) [SIG Node]

- DRA: The scheduler plugin prevented abnormal filter runtimes by timing out after 10 seconds. This was configurable via the plugin configuration's `FilterTimeout`. Setting it to zero disabled the timeout and restored the behavior of Kubernetes <= 1.33. ([#132033](https://github.com/kubernetes/kubernetes/pull/132033), [@pohly](https://github.com/pohly))...