Skip to content
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.

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

[Remote clusters] Add remote cluster UI should not specify transport port #164401

Closed
abdonpijpelink opened this issue Aug 22, 2023 · 1 comment · Fixed by #164442
Closed

[Remote clusters] Add remote cluster UI should not specify transport port #164401

abdonpijpelink opened this issue Aug 22, 2023 · 1 comment · Fixed by #164442
Assignees
Labels
Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@abdonpijpelink
Copy link
Contributor

abdonpijpelink commented Aug 22, 2023

The UI for adding a new remote cluster specifies that users should enter the transport port. However, with the new API key based trust mechanism, local clusters need to connect to a new port on the remote cluster(remote_cluster.port, defaults to 9443) instead of the transport port. Because we don't know in advance what trust mechanism the user will use, maybe we should simply say "port" instead?

image
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 22, 2023
@abdonpijpelink abdonpijpelink changed the title [Remote clusters [Remote clusters] Add remote cluster UI should not specify transport port Aug 22, 2023
@sabarasaba sabarasaba added Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more and removed needs-team Issues missing a team label labels Aug 22, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants