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
Is your feature request related to a problem? Please describe.
Problem statement: ability to seamlessly find and communicate across services in AWS, and services in K8s is something of an unknown at the moment. We can use these libraries to find AWS services within K8s, but could we extend the functionality to be bi-directional.
Describe the solution you would like.
First of all, we'll likely need a discovery implementation for the K8s service discovery API, which should be simple enough, and the ability to resolve etc.
The second element would be, to have multiple service discovery implementations simultaneously. For example, the Cloudmap Discovery, and K8s.
Finally, could we then efficiently check each of the n service discovery registries provided for the requested resource. We could check them one by one, in the order in which they're registered. Or we could allow more granular control at run time to say 'check in K8s for this thing'.
Registering shouldn't be a problem, it would essentially be a no-op for K8s as this is automatic. Or we could allow for users to define their own resource name and map it to a value in k8s.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Problem statement: ability to seamlessly find and communicate across services in AWS, and services in K8s is something of an unknown at the moment. We can use these libraries to find AWS services within K8s, but could we extend the functionality to be bi-directional.
Describe the solution you would like.
First of all, we'll likely need a discovery implementation for the K8s service discovery API, which should be simple enough, and the ability to resolve etc.
The second element would be, to have multiple service discovery implementations simultaneously. For example, the Cloudmap Discovery, and K8s.
Finally, could we then efficiently check each of the n service discovery registries provided for the requested resource. We could check them one by one, in the order in which they're registered. Or we could allow more granular control at run time to say 'check in K8s for this thing'.
Registering shouldn't be a problem, it would essentially be a no-op for K8s as this is automatic. Or we could allow for users to define their own resource name and map it to a value in k8s.
The text was updated successfully, but these errors were encountered: