labels.send_testmail=Wyślij e-mail testowy
labels.backup_configuration=Kopia zapasowa
labels.backup_name=Nazwa
labels.backup_bulk_file=Plik zbiorczy
labels.backup_button_upload=Prześlij
labels.process_time_is_exceeded=Przekroczono limit czasu oczekiwania na wyszukiwanie. Wyświetlone wyniki mogą być częściowe.
labels.user_given_name=Imię (imię własne)
labels.givenName=Imię (imię własne)
labels.user_surname=Nazwisko
labels.surame=Nazwisko

        "stopwords": "_english_"
      },
      "content_length_filter": {
        "type": "length",
        "max": 30
      },
      "limit_token_count_filter": {
        "type": "limit",
        "max_token_count": 2147483647
      },
      "stemmer_en_filter": {
        "type": "stemmer",
        "name": "english"
      },
      "arabic_stop": {
        "type":       "stop",

        "stopwords": "_english_"
      },
      "content_length_filter": {
        "type": "length",
        "max": 30
      },
      "limit_token_count_filter": {
        "type": "limit",
        "max_token_count": 2147483647
      },
      "stemmer_en_filter": {
        "type": "stemmer",
        "name": "english"
      },
      "arabic_stop": {
        "type":       "stop",

    * Custom apiservers built with the latest apiserver library will have the 100MB limit on the body of resource requests as well. The limit can be altered via ServerRunOptions.MaxRequestBodyBytes.
    * The body size limit does not apply to subresources like pods/proxy that proxy request content to another server.

  The possibility of borrowing means that the old metric `apiserver_flowcontrol_request_concurrency_limit` can no longer mean both the configured concurrency limit and the enforced concurrency limit. Henceforth it means the configured concurrency limit.' ([#113485](https://github.com/kubernetes/kubernetes/pull/113485), [@MikeSpreitzer](https://github.com/MikeSpreitzer))

- Fix a bug where CRI implementations that use cAdvisor stats provider (CRI-O) don't evict pods when their logs exceed ephemeral storage limit. ([#108115](https://github.com/kubernetes/kubernetes/pull/108115), [@haircommander](https://github.com/haircommander)) [SIG Node]

* Send recycle events from pod to pv. ([#27714](https://github.com/kubernetes/kubernetes/pull/27714), [@jsafrane](https://github.com/jsafrane))
* Limit the number of names per image reported in the node status ([#32914](https://github.com/kubernetes/kubernetes/pull/32914), [@yujuhong](https://github.com/yujuhong))

labels.backup_configuration=Backup
labels.backup_name=Name
labels.backup_bulk_file=Bulk File
labels.backup_button_upload=Upload
labels.process_time_is_exceeded=The search processing time has exceeded the limit. The displayed results may be partial.
labels.user_given_name=Given Name
labels.givenName=Given Name
labels.user_surname=Surname
labels.surame=Surname
labels.user_mail=Mail
labels.mail=Mail

Kubernetes cgroup manager uses `memory.limit_in_bytes` in v1 cgroups to limit the memory capacity for a container, and uses `oom_scores` to recommend an order for killing container processes if an out-of-memory event occurs. This implementation has shortcomings: for `Guaranteed` pods, memory can not be fully reserved, and the page cache is at risk of being recycled. For `Burstable` pods, overcommitting memory (setting `request` less than `limit` ) could increase the risk of a container being killed when the...

- Limit number of instances in a single update to GCE target pool to 1000. ([#87881](https://github.com/kubernetes/kubernetes/pull/87881), [@wojtek-t](https://github.com/wojtek-t)) [SIG Cloud Provider, Network and Scalability]