@florent-leborgne , I did an analysis of elastic/kibana#233415 and while I agree that it might be worthy to say something in our docs about this Kibana change, I don't think we should highlight this much. These are my impressions:

Elasticsearch already supported IPv6 addresses in their settings, the change is that Kibana UI for remote clusters wasn't supporting them (but this is more a bug / limitation fix than a feature considering ES supported them already and users could configure them with the API).
Even if IPv6 was already supported in Elasticsearch we didn't have anything about it in our docs for remote clusters, so start highlighting now that Kibana UI supports IPv6 for remote clusters feels a bit weird. But just a simple mention should be fine (which is what I've tried to achieve).

With the previous in mind, IMO the Kibana change would fit more in terms of docs:

A simple Release Notes item.
A UX change to highlight directly within Kibana Remote Clusters UI that the field supports ipv6 addresses. --> The best place to highlight this IMO.

Anyway I've created #3361 to address this (and apply the improvements mentioned in the previous comment).

Looking forward to hearing your thoughts.

[Kibana] IPv6 support for remote clusters #3093

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions