You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we're using '@' to determine is the network service or network service endpoint related to the some another (external) domain.
For example,
my-service@my-domain means that my-service is located in the remote domain my-domain.
This is working fine, but we could try to support dns target pattern from the grpc.
dns:[//authority/]host[:port] – DNS (default)
1. host is the host to resolve via DNS.
2. port is the port to return for each address. If not specified, 443 is used (but some implementations default to 80 for insecure channels).
3. authority indicates the DNS server to use, although this is only supported by some implementations. (In C-core, the default DNS resolver does not support this, but the c-ares based resolver supports specifying this in the form "IP:port".)
denis-tingaikin
changed the title
Get rid of using '@' in interdomain NSM scenarious
Use dns target for urls in interdomain and floating interdomain scenarious
Nov 7, 2023
@denis-tingaikin Could you point me to the current URI standard we are using that you are proposing replacing? I'd like to make sure we are covering all the cases reasonably.
Overview
Currently, we're using '@' to determine is the network service or network service endpoint related to the some another (external) domain.
For example,
my-service@my-domain
means that my-service is located in the remote domain my-domain.This is working fine, but we could try to support dns target pattern from the grpc.
Source: https://grpc.github.io/grpc/core/md_doc_naming.html
Example
At this moment endpoint entries in the registry are
With this feature we'll able to use this
Pros/cons
Pors:
Cons:
References
https://networkservicemesh.io/docs/concepts/k8s/
Decomposition
The text was updated successfully, but these errors were encountered: