triggers execution of the statements of the associated case;
the other cases are skipped.
If no case matches and there is a "default" case,
its statements are executed.
There can be at most one default case and it may appear anywhere in the
"switch" statement.
A missing switch expression is equivalent to the boolean value
<code>true</code>.
</p>

<pre class="ebnf">

Before Starlette `0.24.0`, a new instance of each middleware class would be created when a new middleware was added. That normally was not a problem, unless the middleware class expected to be created only once, with only one instance, that happened in some cases. This upgrade would solve those cases (thanks [@adriangb](https://github.com/adriangb)! Starlette PR [#2017](https://github.com/encode/starlette/pull/2017)). Now the middleware class instances are created once, right before the first request...

- Immediately close the other side of the connection when proxying. ([#67288](https://github.com/kubernetes/kubernetes/pull/67288), [@MHBauer](https://github.com/MHBauer))

    <tika:uti>com.sun.java-archive</tika:uti>
    <sub-class-of type="application/zip"/>
    <glob pattern="*.jar"/>
  </mime-type>

  <mime-type type="application/vnd.android.package-archive">
    <sub-class-of type="application/java-archive"/>
    <glob pattern="*.apk"/>
  </mime-type>
  <mime-type type="application/x-tika-java-enterprise-archive">
    <sub-class-of type="application/java-archive"/>
    <glob pattern="*.ear"/>

  // to run this pod.  If no RuntimeClass resource matches the named class, the pod will not be run.
  // If unset or empty, the "legacy" RuntimeClass will be used, which is an implicit class with an
  // empty definition that uses the default runtime handler.
  // More info: https://git.k8s.io/enhancements/keps/sig-node/585-runtime-class
  // +optional
  optional string runtimeClassName = 29;

    * "volume.alpha.kubernetes.io/storage-class" does not have any special meaning. A default storage class
    * and  DefaultStorageClass admission plugin can be used to preserve similar behavior of Kubernetes cluster,
    * see https://kubernetes.io/docs/user-guide/persistent-volumes/#class-1 for details.

    String LDAP_ADMIN_USER_BASE_DN = "ldap.admin.user.base.dn";

    /** The key of the configuration. e.g. organizationalPerson,top,person,inetOrgPerson */
    String LDAP_ADMIN_USER_OBJECT_CLASSES = "ldap.admin.user.object.classes";

    /** The key of the configuration. e.g. cn=%s */
    String LDAP_ADMIN_ROLE_FILTER = "ldap.admin.role.filter";

    /** The key of the configuration. e.g. ou=Role,dc=fess,dc=codelibs,dc=org */

    *  - vSphere cloud provider (VCP) uses OS hostname and not vSphere Inventory VM Name.
    *    That means, now  VCP can handle cases where user changes VM inventory name.
    * - VCP can handle cases where VM migrates to other ESXi cluster or datacenter or vCenter.
    * The only requirement is the shared storage. VCP needs shared storage on all Node VMs.

following in mind:

* **JSON configuration files that contain fields with incorrect case will no longer be valid. You must correct these files before upgrading.** When specifying keys in JSON resource definitions during direct API server communication, the keys are case-sensitive. A bug introduced in Kubernetes 1.8 caused the API server to accept a request with incorrect case and coerce it to correct case, but this behaviour has been fixed in 1.11 and the API server will once again be enforcing...

### Other notable changes

* Kubernetes json deserializer is now case-sensitive to restore compatibility with pre-1.8 servers. ([#65157](https://github.com/kubernetes/kubernetes/pull/65157), [@caesarxuchao](https://github.com/caesarxuchao))
    * If your config files contains fields with wrong case, the config files will be now invalid.