feat(plugins): add a cluster node list with failover to Elasticsearch

[datlechin]

Why

An Elasticsearch connection took one Host and Port, so a cluster could not be entered and one down node broke the connection. The form treated only MongoDB's host list as the endpoint, so Kafka's list hid Host and Port while its driver still dialed a hidden localhost:9092 first.

Change

• Elasticsearch: a Hosts list, as host:port or a pasted URL. It connects to the first node that answers. Reads move to the next node; writes move only when they never reached a node. An https:// row needs SSL turned on.
• Any host list without a visibility rule stands in for Host and Port: seeded from them, Host and Port taken from its first row, blank rows dropped, invalid rows block Save.
• Kafka: Bootstrap Servers replaces the hidden Host, which an existing list keeps as its last row. One dead broker no longer uses up the whole connect timeout.
• An Elasticsearch console path starting with // no longer sends the Authorization header to another host.

Verified

EndpointHostListFormTests, ElasticsearchFailoverTests (local HTTP nodes) and HostListEndpointTests fail on main. No UI test or screenshots: both drivers are registry-only and a sandboxed Debug build cannot install them; the host-list row is the one RedisConnectionModeUITests drives.

Not in this PR

• Registry releases of the Elasticsearch and Kafka plugins.
• Verify CA ignores the CA file in Elasticsearch, Typesense and Weaviate.
• IPv6 hosts in Typesense and etcd URLs.

Fixes #3281

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
TablePro	🟢 Ready	View Preview	Oct 8, 2026, 10:49 AM

💡 Tip: Enable Automations to automatically generate PRs for you.