-
Notifications
You must be signed in to change notification settings - Fork 347
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
Resolve Service to Endpoints IPs #35
Comments
The service resolver is currently the responsibility of a provider. I'm moving this issue to the backlog for now. |
@arkodg can this issue be closed? |
we dont need a full fledged service resolver design & implementation, but a reconciler within |
I suggest holding this issue until #702 is merged. |
@zhshw can you help with this issue ? |
@arkodg I'm working on it... |
thanks @zhshw .
|
Thanks @arkodg reply. The endpoint is updated frequently. It should be an independent workqueue. endpoint-slices
Before Kubernetes v1.26 Kubernetes >= v1.21 Kubernetes General version Istio compatibility Improvement Goal Node NotReady Finally, Things don't seem so simple... [Performance, Compatibility, Coding cost] |
Since we will need an abstraction to supports multiple implementations, WDYT about starting off with endpoints instead of endpoint slices and iterating? We could introduce endpointslices thereafter. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
@zhshw I just cleared the stale status for this issue. Are you still planning to work on this? |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
unassigning @zhshw for now, will reassign again if interested, adding the |
closing in favor of #1256 |
#16 specifies the need for a Service Resolver (SR) component that resolves IR services into platform-specific endpoints. The SR details should be captured in this issue or a linked doc.
The text was updated successfully, but these errors were encountered: