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.

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

Jump to bottom

Naming clash & resolution strategy for Multi-Peer Exported Services #123

Open
bartoszmajsak opened this issue Jan 10, 2025 · 0 comments
Open

Naming clash & resolution strategy for Multi-Peer Exported Services #123

bartoszmajsak opened this issue Jan 10, 2025 · 0 comments
Labels
area/discovery enhancement New feature or request

Comments

@bartoszmajsak
Copy link
Collaborator

Currently, if multiple remotes export the same service (in the same namespace), but with different resolution strategies (static vs. DNS) or varying service ports, there is no clear handling mechanism.

A feasible solution is to enforce STATIC resolution and resolve addresses as DNS names.
@bartoszmajsak bartoszmajsak added enhancement New feature or request area/discovery labels Jan 10, 2025
@bartoszmajsak bartoszmajsak mentioned this issue Jan 10, 2025
Merged
@bartoszmajsak bartoszmajsak changed the title Naming Clash & Resolution Strategy for Multi-Peer Exported Services Naming clash & resolution strategy for Multi-Peer Exported Services Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/discovery enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bartoszmajsak