## Deployment Strategies

There are several ways to do it depending on your specific use case and the tools that you use.

You could **deploy a server** yourself using a combination of tools, you could use a **cloud service** that does part of the work for you, or other possible options.

apiServerExtraArgs:
  cloud-provider: "{cloud}"
  cloud-config: "{cloud-config-path}"
apiServerExtraVolumes:
- name: cloud
  hostPath: "{cloud-config-path}"
  mountPath: "{cloud-config-path}"
controllerManagerExtraArgs:
  cloud-provider: "{cloud}"
  cloud-config: "{cloud-config-path}"
controllerManagerExtraVolumes:
- name: cloud
  hostPath: "{cloud-config-path}"

                "<script type=\"text/javascript\">" +
                "const btn = document.querySelector('.theme-toggle');" +
                "const prefersDarkScheme = window.matchMedia('(prefers-color-scheme: dark)');" +
                "const currentTheme = localStorage.getItem('theme');" +
                "if (currentTheme == 'dark') {" +
                "    document.body.classList.toggle('dark-theme');" +

## Verifique a documentação automática da API

Agora, execute `uvicorn`, usando o módulo `app.main` e a variável `app`:

<div class="termy">

```console
$ uvicorn app.main:app --reload

<span style="color: green;">INFO</span>:     Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
```

</div>

- The cloud config for Azure cloud provider can now be initialized from Kubernetes secret azure-cloud-provider in kube-system namespace
    - the secret is a serialized version of `azure.json` file with key cloud-config. And the secret name is azure-cloud-provider.

@AndroidIncompatible // TODO(b/230620681): Make this available (even though we won't run it).
public class SourceSinkTester<S, T, F extends SourceSinkFactory<S, T>> extends TestCase {

  static final String LOREM_IPSUM =
      "Lorem ipsum dolor sit amet, consectetur adipiscing "
          + "elit. Cras fringilla elit ac ipsum adipiscing vulputate. Maecenas in lorem nulla, ac "
          + "sollicitudin quam. Praesent neque elit, sodales quis vestibulum vel, pellentesque nec "

  - 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.

    'round(%s, %s)' % [query, by],
  quantile(quantile, query):
    'histogram_quantile(%s, %s)' %[quantile, query],
  labels(metric_name, labels):
    // One can nest locals.
    // Every local ends with a semi-colon.
    local prom_labels = std.join(',',
      std.map(
        function(k)
          if std.startsWith(labels[k], "!~") then
            '%s!~"%s"'%[ k, std.lstripChars(labels[k], '!~')]

        "da - jordbær fløde på", // x
        "de - Zwölf Boxkämpfer", // x
        "el - Γαζέες καὶ μυρτιὲς", // x
        "es - pingüino kilómetros frío, añoraba", // x
        "fr - cœur déçu lâme plutôt naïveæ", // x
        "ga - Íosa, Úrmhac na hÓighe, pór Éava Ádhaimh", // x
        "hu - Árvíztűrő tükörfúrógép", // x
        "is - Kæmi ný öxi hér ykist þjófum nú bæði víl og ádrepa", // x

* Deprecate auto detecting cloud providers in kubelet. Auto detecting cloud providers go against the initiative for out-of-tree cloud providers as we'll now depend on cAdvisor integrations with cloud providers instead of the core repo. In the near future, `--cloud-provider` for kubelet will either be an empty string or `external`.  ([#51312](https://github.com/kubernetes/kubernetes/pull/51312),...