* if the new state is "partialDisruption" or "fullDisruption" we call a user defined function that returns a new QPS to use (default 1/10 of the default rate, and the default rate respectively),
      * if the new state is "normal" we resume normal operation (go back to default limiter settings),
      * if all zones in the cluster are in "fullDisruption" state we stop all evictions.

- client-go discovery clients constructed using `NewDiscoveryClientForConfig` or `NewDiscoveryClientForConfigOrDie` default to rate limits that cause normal discovery request patterns to take several seconds. This is fixed in https://issue.k8s.io/86168 and will be resolved in v1.17.1. As a workaround, the `Burst` value can be adjusted higher in the rest.Config passed into `NewDiscoveryClientForConfig`...

   *     cancelled regardless
   * @return {@code false} if the step could not be cancelled, typically because it has already
   *     completed normally; {@code true} otherwise
   */
  @CanIgnoreReturnValue
  @SuppressWarnings("Interruption") // We are propagating an interrupt from a caller.
  public boolean cancel(boolean mayInterruptIfRunning) {

## Changes since v1.3.0-beta.1

### Experimental Features

* Init containers enable pod authors to perform tasks before their normal containers start. Each init container is started in order, and failing containers will prevent the application from starting. ([#23666](https://github.com/kubernetes/kubernetes/pull/23666), [@smarterclayton](https://github.com/smarterclayton))

    * This allows adding extra code after a dependency is done. It can be used, for example, to close database connections.
    * Dependencies with `yield` can be normal or `async`, **FastAPI** will run normal dependencies in a threadpool.
    * They can be combined with normal dependencies.
    * It's possible to have arbitrary trees/levels of dependencies with `yield` and exit steps are handled in the correct order automatically.

   * Highly specific magic matches get a high priority
   * General magic matches which could trigger a false-positive need
     a low one
   * The priority for containers normally need to be higher than for
     the things they contain, so they don't accidently get detected
     as what's in them
   * For logic too complex to be expressed in a magic match, do the best

          "type" : "synonym_graph",
          "synonyms": ["fess,フエス"]
        }
      },
      "tokenizer": {
        "japanese_tokenizer": {
          "type": "kuromoji_tokenizer",
          "mode": "normal",
          "discard_punctuation": false,
          "user_dictionary_rules": ["令和,令和,レイワ,名詞-固有名詞-一般", "日本経済新聞,日本 経済 新聞,ニホン ケイザイ シンブン,カスタム名詞", "関西国際空港,関西 国際 空港,カンサイ コクサイ クウコウ,テスト名詞", "朝青龍,朝青龍,アサショウリュウ,カスタム名詞"]
        },

          "type" : "synonym_graph",
          "synonyms": ["fess,フエス"]
        }
      },
      "tokenizer": {
        "japanese_tokenizer": {
          "type": "kuromoji_tokenizer",
          "mode": "normal",
          "discard_punctuation": false,
          "user_dictionary_rules": ["令和,令和,レイワ,名詞-固有名詞-一般", "日本経済新聞,日本 経済 新聞,ニホン ケイザイ シンブン,カスタム名詞", "関西国際空港,関西 国際 空港,カンサイ コクサイ クウコウ,テスト名詞", "朝青龍,朝青龍,アサショウリュウ,カスタム名詞"]
        },

      if (value == null) {
        tryDrainReferenceQueues();
        return null;
      }

      return value;
    }

    /**
     * Performs routine cleanup following a read. Normally cleanup happens during writes, or from
     * the cleanupExecutor. If cleanup is not observed after a sufficient number of reads, try
     * cleaning up from the read thread.
     */
    void postReadCleanup() {

* Fixes a flaw (CVE-2019-11253) in json/yaml decoding where large or malformed documents could consume excessive server resources. Request bodies for normal API requests (create/delete/update/patch operations of regular resources) are now limited to 3MB. ([#83261](https://github.com/kubernetes/kubernetes/pull/83261), [@liggitt](https://github.com/liggitt))



# v1.16.1