* Ha nem akkor látni fogunk egy tiszta hibát ezzel kapcsolatban.
* ellenőrzi hogyha van egy opcionális query paraméter `q` névvel (azaz `http://127.0.0.1:8000/items/foo?q=somequery`) `GET` kérések esetén.
    * Mivel a `q` paraméter `= None`-al van deklarálva, ezért opcionális.
    * `None` nélkül ez a mező kötelező lenne (mint például a body `PUT` kérések esetén).

* DELETE requests can now pass in their DeleteOptions as a query parameter or a body parameter, rather than just as a body parameter. ([#35806](https://github.com/kubernetes/kubernetes/pull/35806), [@bdbauer](https://github.com/bdbauer))

labels.cronExpression=スケジュール
labels.dayForCleanup=指定日以前のドキュメントの削除
labels.crawlingThreadCount=同時クロール数
labels.boost=ブースト値
labels.crawlingConfigName=名前
labels.crawlingConfigPath=クロールするパス
labels.processType=処理の種類
labels.parameters=パラメーター
labels.designFile=アップロードするファイル
labels.bulkFile=バルクファイル
labels.appendQueryParameter=検索パラメーターの追加
labels.configId=設定ID
labels.configParameter=設定パラメーター
labels.content=コンテンツ
labels.csvFileEncoding=CSVエンコーディング

administrators will be able to place limits by using the new kubelet command line parameter --pod-max-pids. Note that since this is a alpha feature they will need to enable the "SupportPodPidsLimit" feature. By default, we do not set any maximum limit, If an administrator wants to enable this, they should enable SupportPodPidsLimit=true in the --feature-gates= parameter to kubelet and specify the limit using the --pod-max-pids parameter. The limit set is the total count of all processes running in all containers...

- ACTION REQUIRED for custom scheduler plugin developers:
  `EventsToRegister` in the `EnqueueExtensions` interface gets `ctx` in the parameters and `error` in the return values.

*   Issues a warning when the `session_config` parameter for the TF1 converter
    is used or the `rewrite_config_template` field in the TF2 converter
    parameter object is used.

### TPU Enhancements:

*   Adds support for the `beta` parameter of the FTRL optimizer for TPU
    embeddings. Users of other TensorFlow platforms can implement equivalent
    behavior by adjusting the `l2` parameter.

### XLA Support:

    ```
    Storage class spec:
    kind: StorageClass
    apiVersion: storage.k8s.io/v1
    metadata:
      name: fastpolicy1
    provisioner: kubernetes.io/vsphere-volume
    parameters:
        diskformat: zeroedthick
        storagePolicyName: vSAN Default Storage Policy
    allowedTopologies:
    - matchLabelExpressions:
      - key: failure-domain.beta.kubernetes.io/zone
        values:

- The `IngressClassNamespacedParams` feature gate has graduated to beta and is enabled by default. This means IngressClass resource will now have two new fields - `spec.paramters.namespace` and `spec.parameters.scope`. ([#101711](https://github.com/kubernetes/kubernetes/pull/101711), [@hbagdi](https://github.com/hbagdi))

  <mime-type type="application/x-x509-dsa-parameters">
    <magic priority="50">
      <!-- PEM encoded only -->
      <match value="-----BEGIN DSA PARAMETERS-----" type="string" offset="0"/>
    </magic>
  </mime-type>
  <mime-type type="application/x-x509-ec-parameters">
    <magic priority="50">
      <!-- PEM encoded only -->
      <match value="-----BEGIN EC PARAMETERS-----" type="string" offset="0"/>
    </magic>

```Python
= None
```

ou :

```Python
= Query(None)
```

et utilisera ce `None` pour détecter que ce paramètre de requête **n'est pas requis**.

Le `Union[str, None]` est uniquement là pour permettre à votre éditeur un meilleur support.

///