<class>
      <name>PluginContainer</name>
      <version>3.0.0+</version>
      <description>Contains the plugins information for the project.</description>
      <fields>
        <field>
          <name>plugins</name>
          <version>4.0.0+</version>
          <description>The list of plugins to use.</description>
          <association>
            <type>Plugin</type>
            <multiplicity>*</multiplicity>

                    }
                    final File pluginDir = new File(esDir, "plugins");
                    if (pluginDir.isDirectory()) {
                        settingsBuilder.put("path.plugins", pluginDir.getAbsolutePath());
                    } else {
                        settingsBuilder.put("path.plugins", new File(System.getProperty("user.dir"), "plugins").getAbsolutePath());
                    }

- Extended resources requested by initContainers which are allocated using an automatic ResourceClaim now match the behavior of legacy device plugins, reusing the same resources requested by later sidecar initContainers or regular containers when possible, to minimize the total number of devices requested by the pod. ([#134882](https://github.com/kubernetes/kubernetes/pull/134882), [@yliaog](h...

* The deprecated kubelet --configure-cbr0 flag has been removed, and with that the "classic" networking mode as well.  If you depend on this mode, please investigate whether the other network plugins `kubenet` or `cni` meet your needs. ([#34906](https://github.com/kubernetes/kubernetes/pull/34906), [@luxas](https://github.com/luxas))

    /** The key of the message: Failed to install {0}. */
    public static final String ERRORS_failed_to_install_plugin = "{errors.failed_to_install_plugin}";

    /** The key of the message: Could not find available plugins. */
    public static final String ERRORS_failed_to_find_plugins = "{errors.failed_to_find_plugins}";

    /** The key of the message: Failed to process a request: {0} */

  - Easier to understand a cluster (eg: API audit logs, server-based API defaults)
- **Stateful Application Support**
  - Enhanced persistence capabilities (eg: `StorageClasses`, new volume plugins)
  - New resources and scheduler features (eg: `ScheduledJob` resource, pod/node affinity/anti-affinity)
- **Cluster Federation**
  - Global Multi-cluster HTTP(S) Ingress across GCE and GKE clusters.