Mas é possível personalizá-los, você pode definir um CDN específico ou providenciar os arquivos você mesmo.

## CDN Personalizado para JavaScript e CSS

A **request** body is data sent by the client to your API. A **response** body is the data your API sends to the client.

Your API almost always has to send a **response** body. But clients don't necessarily need to send **request bodies** all the time, sometimes they only request a path, maybe with some query parameters, but don't send a body.

All metrics returned are from server-side reports. This means that latencies
and error rates are from the perspective of the service itself and not of an
individual client (or aggregate set of clients). Rates and latencies are
calculated over a time interval of 1 minute.
`,
		Example: `  # Retrieve workload metrics for productpage-v1 workload
  istioctl experimental metrics productpage-v1

  // pods of a disrupted application might not get a chance to become healthy.
  // Healthy pods will be subject to the PDB for eviction.
  //
  // Additional policies may be added in the future.
  // Clients making eviction decisions should disallow eviction of unhealthy pods
  // if they encounter an unrecognized policy in this field.
  //
  // This field is beta-level. The eviction API uses this field when

 * files to be deleted. The limit does not include filesystem overhead or the cache journal so
 * space-sensitive applications should set a conservative limit.
 *
 * Clients call [edit] to create or update the values of an entry. An entry may have only one editor
 * at one time; if a value is not available to be edited then [edit] will return null.
 *

}}{{ end }} {{- if eq .Values.gateway.type "gcs" }} {{- if .Values.gateway.gcs.serviceAccountFile }} service-account-file.json: {{ .Values.gateway.gcs.serviceAccountFile | b64enc }} {{- end }} {{- end }} {{- if .Values.etcd.clientCert }} etcd_client.crt: {{ .Values.etcd.clientCert | toString | b64enc | quote }} {{- end }} {{- if .Values.etcd.clientCertKey }} etcd_client.key: {{ .Values.etcd.clientCertKey | toString | b64enc | quote }} {{- end }} {{- end }} minio/templates/securitycontextconst.yaml {{-...

}}{{ end }} {{- if eq .Values.gateway.type "gcs" }} {{- if .Values.gateway.gcs.serviceAccountFile }} service-account-file.json: {{ .Values.gateway.gcs.serviceAccountFile | b64enc }} {{- end }} {{- end }} {{- if .Values.etcd.clientCert }} etcd_client.crt: {{ .Values.etcd.clientCert | toString | b64enc | quote }} {{- end }} {{- if .Values.etcd.clientCertKey }} etcd_client.key: {{ .Values.etcd.clientCertKey | toString | b64enc | quote }} {{- end }} {{- end }} minio/templates/securitycontextconst.yaml {{-...

}}{{ end }} {{- if eq .Values.gateway.type "gcs" }} {{- if .Values.gateway.gcs.serviceAccountFile }} service-account-file.json: {{ .Values.gateway.gcs.serviceAccountFile | b64enc }} {{- end }} {{- end }} {{- if .Values.etcd.clientCert }} etcd_client.crt: {{ .Values.etcd.clientCert | toString | b64enc | quote }} {{- end }} {{- if .Values.etcd.clientCertKey }} etcd_client.key: {{ .Values.etcd.clientCertKey | toString | b64enc | quote }} {{- end }} {{- end }} minio/templates/securitycontextconst.yaml {{-...

            * **FastAPI** fügt hier eine Referenz auf die globalen JSON-Schemas an einer anderen Stelle in Ihrer OpenAPI hinzu, anstatt es direkt einzubinden. Auf diese Weise können andere Anwendungen und Clients diese JSON-Schemas direkt verwenden, bessere Tools zur Codegenerierung bereitstellen, usw.

///

Die generierten Responses in der OpenAPI für diese *Pfadoperation* lauten:

```JSON hl_lines="3-12"
{

            * **FastAPI** adds a reference here to the global JSON Schemas in another place in your OpenAPI instead of including it directly. This way, other applications and clients can use those JSON Schemas directly, provide better code generation tools, etc.

///

The generated responses in the OpenAPI for this *path operation* will be:

```JSON hl_lines="3-12"
{
    "responses": {