# FastAPI bei Cloudanbietern deployen { #deploy-fastapi-on-cloud-providers }

Sie können praktisch **jeden Cloudanbieter** verwenden, um Ihre FastAPI-Anwendung bereitzustellen.

In den meisten Fällen bieten die großen Cloudanbieter Anleitungen zum Deployment von FastAPI an.

## FastAPI Cloud { #fastapi-cloud }

**<a href="https://fastapicloud.com" class="external-link" target="_blank">FastAPI Cloud</a>** wurde vom selben Autor und Team hinter **FastAPI** entwickelt.

Вы можете использовать практически любого облачного провайдера, чтобы развернуть свое приложение на FastAPI.

В большинстве случаев у основных облачных провайдеров есть руководства по развертыванию FastAPI на их платформе.

## FastAPI Cloud { #fastapi-cloud }

# Deploy FastAPI on Cloud Providers { #deploy-fastapi-on-cloud-providers }

You can use virtually **any cloud provider** to deploy your FastAPI application.

In most of the cases, the main cloud providers have guides to deploy FastAPI with them.

## FastAPI Cloud { #fastapi-cloud }

**<a href="https://fastapicloud.com" class="external-link" target="_blank">FastAPI Cloud</a>** is built by the same author and team behind **FastAPI**.

Puedes usar prácticamente **cualquier proveedor de nube** para desplegar tu aplicación FastAPI.

En la mayoría de los casos, los principales proveedores de nube tienen guías para desplegar FastAPI con ellos.

## FastAPI Cloud { #fastapi-cloud }

# Implantar FastAPI em provedores de nuvem { #deploy-fastapi-on-cloud-providers }

Você pode usar praticamente **qualquer provedor de nuvem** para implantar seu aplicativo FastAPI.

Na maioria dos casos, os principais provedores de nuvem têm tutoriais para implantar o FastAPI com eles.

## FastAPI Cloud { #fastapi-cloud }

rnetes/kubernetes/pull/58502), [@dixudx](https://github.com/dixudx))

* Authentication information for OpenStack cloud provider can now be specified as environment variables. When we convert the OpenStack cloud provider to run in an external process, we can now use the kubernetes Secrets capability to inject the OS_* variables. This way we can specify the cloud configuration as a configmap, and specify secrets for the userid/password information. The configmap is mounted as a file, and...

* vSphere cloud provider: Remove the dependency of login information on worker nodes for vsphere cloud provider. ([#43545](https://github.com/kubernetes/kubernetes/pull/43545), [@luomiao](https://github.com/luomiao))

onsole.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler) | [amd64](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-amd64), [arm](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-arm), [arm64](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-arm64), [ppc64le](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-ppc64le), [s390x](https://console.cloud.google....

* Fix space issue in volumePath with vSphere Cloud Provider ([#38338](https://github.com/kubernetes/kubernetes/pull/38338), [@BaluDontu](https://github.com/BaluDontu))
* Fix panic in vSphere cloud provider ([#38423](https://github.com/kubernetes/kubernetes/pull/38423), [@BaluDontu](https://github.com/BaluDontu))

  - example manifests for the kube-apiserver, kube-controller-manager, kube-schedule, kubelet, and the cloud-controller-manager
  - labels/annotations that are consumed by any cloud specific controllers

In addition to the above, SIG Cloud Provider has been focusing on a long running effort to remove cloud provider code from kubernetes/kubernetes.