And the rest will be handled by **FastAPI**.

If you run it and go to [http://localhost:8000/v1/](http://localhost:8000/v1/) you will see the response from Flask:

```txt
Hello, World from Flask!
```

And if you go to [http://localhost:8000/v2](http://localhost:8000/v2) you will see the response from FastAPI:

```JSON
{
    "message": "Hello World"
}

///

## 試試看 { #check-it }

現在，位於路徑 `/v1/` 底下的所有請求都會由 Flask 應用處理。

其餘則由 **FastAPI** 處理。

如果你啟動它並前往 [http://localhost:8000/v1/](http://localhost:8000/v1/)，你會看到來自 Flask 的回應：

```txt
Hello, World from Flask!
```

如果你前往 [http://localhost:8000/v2](http://localhost:8000/v2)，你會看到來自 FastAPI 的回應：

```JSON
{
    "message": "Hello World"
}

///

## 检查 { #check-it }

现在，所有定义在 `/v1/` 路径下的请求将会被 Flask 应用处理。

其余的请求则会被 **FastAPI** 处理。

如果你运行它并访问 [http://localhost:8000/v1/](http://localhost:8000/v1/)，你将会看到由 Flask 返回的响应：

```txt
Hello, World from Flask!
```

如果你访问 [http://localhost:8000/v2](http://localhost:8000/v2)，你将会看到由 FastAPI 返回的响应：

```JSON
{
    "message": "Hello World"
}

not setting the flag, no action is necessary. ([#88290](https://github.com/kubernetes/kubernetes/pull/88290), [@tallclair](https://github.com/tallclair)) [SIG API Machinery and Node]

- `kubectl` no longer defaults to `http://localhost:8080`.  If you own one of these legacy clusters, you are *strongly- encouraged to secure your server.   If you cannot secure your server, you can set `KUBERNETES_MASTER` if you were relying on that behavior and you're client-go user. Set `--server`, `--kubeconfig`...

А решта - **FastAPI**.

Якщо ви запустите це й перейдете на [http://localhost:8000/v1/](http://localhost:8000/v1/), ви побачите відповідь від Flask:

```txt
Hello, World from Flask!
```

А якщо ви перейдете на [http://localhost:8000/v2](http://localhost:8000/v2), ви побачите відповідь від FastAPI:

```JSON
{
    "message": "Hello World"
}

Y el resto será manejado por **FastAPI**.

Si lo ejecutas y vas a [http://localhost:8000/v1/](http://localhost:8000/v1/) verás el response de Flask:

```txt
Hello, World from Flask!
```

Y si vas a [http://localhost:8000/v2](http://localhost:8000/v2) verás el response de FastAPI:

```JSON
{
    "message": "Hello World"
}

Et le reste sera géré par **FastAPI**.

Si vous l'exécutez et allez à [http://localhost:8000/v1/](http://localhost:8000/v1/) vous verrez la réponse de Flask :

```txt
Hello, World from Flask!
```

Et si vous allez à [http://localhost:8000/v2](http://localhost:8000/v2) vous verrez la réponse de FastAPI :

```JSON
{
    "message": "Hello World"
}

///

## 확인하기 { #check-it }

이제 `/v1/` 경로에 있는 모든 요청은 Flask 애플리케이션에서 처리됩니다.

그리고 나머지는 **FastAPI**에 의해 처리됩니다.

실행하고 [http://localhost:8000/v1/](http://localhost:8000/v1/)로 이동하면 Flask의 응답을 볼 수 있습니다:

```txt
Hello, World from Flask!
```

그리고 [http://localhost:8000/v2](http://localhost:8000/v2)로 이동하면 **FastAPI**의 응답을 볼 수 있습니다:

```JSON
{
    "message": "Hello World"
}

А всё остальное будет обрабатываться **FastAPI**.

Если вы запустите это и перейдёте по [http://localhost:8000/v1/](http://localhost:8000/v1/), вы увидите HTTP‑ответ от Flask:

```txt
Hello, World from Flask!
```

А если вы перейдёте по [http://localhost:8000/v2](http://localhost:8000/v2), вы увидите HTTP‑ответ от FastAPI:

```JSON
{
    "message": "Hello World"
}

E o resto será manipulado pelo **FastAPI**.

Se você rodar a aplicação e ir até [http://localhost:8000/v1/](http://localhost:8000/v1/), você verá o retorno do Flask:

```txt
Hello, World from Flask!
```

E se você for até [http://localhost:8000/v2](http://localhost:8000/v2), você verá o retorno do FastAPI:

```JSON
{
    "message": "Hello World"
}