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

Imp: k8s service discovery across namespaces, using different labels btw provider and consumer #512

Closed
sxllwx opened this issue May 15, 2020 · 1 comment · Fixed by #577
Closed

Imp: k8s service discovery across namespaces, using different labels btw provider and consumer #512

sxllwx opened this issue May 15, 2020 · 1 comment · Fixed by #577
Assignees
@sxllwx

Comments

@sxllwx
Copy link
Member

sxllwx commented May 15, 2020

What would you like to be added:

  1. Service discovery across namespaces.
  2. Transition from the original ListAndWatch to Informer.

Why is this needed:

  1. The native ListAndWatch is not elegant enough, and the more cloud-native solution is to use Informer.
  2. Some classmates in the community responded that they need to be able to specify namespaces or cross-namespaces for service discovery and registration.
@sxllwx sxllwx self-assigned this May 15, 2020
@sxllwx sxllwx mentioned this issue Jun 1, 2020
Merged
@sxllwx
Copy link
Member Author

sxllwx commented Jun 23, 2020

PR merged, Closed

@sxllwx sxllwx closed this as completed Jun 23, 2020
@AlexStocks AlexStocks changed the title Enhance: k8s registry Imp: k8s service discovery across namespaces, using different labels btw provider and consumer Jul 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sxllwx sxllwx

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ftr: using different labels btw provider and consumer, k8s service discovery across namespaces
1 participant
@sxllwx