Skip to content

Discovery v2 - hightlight port change #2091

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 3, 2025
Merged

Discovery v2 - hightlight port change #2091

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0d3bec1
Discovery v2 - hightlight port change
sumyiren Jan 31, 2025
39c1182
Apply suggestions from code review
yirensum Feb 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions modules/ROOT/pages/clustering/setup/discovery.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ The new version v2 introduces the following configuration settings to control th
Possible values are `V1_ONLY`, `V2_ONLY`, `V1_OVER_V2`, and `V2_OVER_V1`.
* xref:configuration/configuration-settings.adoc#config_dbms.kubernetes.discovery.v2.service_port_name[`dbms.kubernetes.discovery.v2.service_port_name`] to specify the name of the service port name used in the Kubernetes API when using version v2.

xref:configuration/ports.adoc[`Ports`] have also changed in discovery v2.
Cluster discovery v1 port is no longer in used (port 5000).
Instead discovery v2 now uses the Cluster internal traffic port (port 6000).

The following sections describe the different methods for server discovery, configuration settings, and examples of how to move from discovery service v1 to v2.

[[clustering-discovery-methods]]
Expand Down