or GA.
  * New Flex Volume Plugin enables users to use out-of-process volume plugins that
are installed to “/usr/libexec/kubernetes/kubelet-plugins/volume/exec/” on
every node, instead of being compiled into the Kubernetes binary. See [example](examples/volumes/flexvolume/README.md) for details.
  * vendor volumes into a pod. It expects vendor drivers are installed in the

success.reindex_started=Started re-indexing.
success.bulk_process_started=Started a bulk process.
success.print_thread_dump=Printed a thread dump to a log file.
success.install_plugin=Installing plugin {0}.
success.delete_plugin=Deleting plugin {0}.
success.upload_file_to_storage=Uploaded {0}.
success.sso_logout=You have been logged out.
success.update_storage_tags=Updated tags of {0}.

success.crud_create_crud_table = Created the data.

success.reindex_started=Started re-indexing.
success.bulk_process_started=Started a bulk process.
success.print_thread_dump=Printed a thread dump to a log file.
success.install_plugin=Installing plugin {0}.
success.delete_plugin=Deleting plugin {0}.
success.upload_file_to_storage=Uploaded {0}.
success.sso_logout=You have been logged out.
success.update_storage_tags=Updated tags of {0}.

success.crud_create_crud_table = Created the data.

- Fixed a regression since 1.24 in the scheduling framework when overriding MultiPoint plugins (e.g. default plugins).

- **Elasticsearch / OpenSearch** - Direct data migration via bulk APIs
- **Apache Solr** - Document import via REST API
- **Database Systems** - Direct connection via DataStore plugins
- **File Systems** - SMB, FTP, local file crawling
- **Custom Systems** - REST API for bulk document indexing

---

## Pre-Migration Planning

### 1. Assessment Phase

- [migration phase 1] PodFitsHostPorts as filter plugin ([#83659](https://github.com/kubernetes/kubernetes/pull/83659), [@wgliang](https://github.com/wgliang))
- [migration phase 1] PodFitsResources as framework plugin ([#83650](https://github.com/kubernetes/kubernetes/pull/83650), [@wgliang](https://github.com/wgliang))

    private static final String[] CAT_NAMES =
            { "aliases", "allocation", "count", "fielddata", "health", "indices", "master", "nodeattrs", "nodes", "pending_tasks",
                    "plugins", "recovery", "repositories", "thread_pool", "shards", "segments", "snapshots", "templates" };

    // ===================================================================================

    install_command_retries: 5
  )
end

def dnf_docker(config)
  config.vm.provision 'install Docker using dnf', type: 'shell', inline: <<-SHELL
    # Install prerequisites
    dnf -y install dnf-plugins-core

    # Add repository
    dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo

    # Install Docker
    dnf install -y docker-ce docker-ce-cli containerd.io

* Added support to a hierarchy of kubectl plugins (a tree of plugins as children of other plugins). ([#45981](https://github.com/kubernetes/kubernetes/pull/45981), [@fabianofranz](https://github.com/fabianofranz))
    * Added exported env vars to kubectl plugins so that plugin developers have access to global flags, namespace, the plugin descriptor and the full path to the caller binary.

    win_def_file = ":tensorflow_filtered_def_file",
)

# To avoid duplication, check that the C++ or python library does not depend on
# the stream executor cuda plugins. Targets that want to use cuda APIs should
# instead depend on the dummy plugins in //tensorflow/compiler/xla/tsl/platform/default/build_config
# and use header only targets.
# TODO(ddunleavy): This seems completely broken. :tensorflow_cc depends on