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.

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

What is the difference between platform registration and client registration of SC in K8? #1367

Open
shri-arunraj opened this issue Jan 2, 2023 · 1 comment

Comments

@shri-arunraj
Copy link

Hello,

Im trying to deploy SC in K8. I have already deployed with platform registration mode as documented here https://service-center.readthedocs.io/en/latest/dev-guides/helm.html?highlight=platform#platform-registration.

In the SC UI web console dashboard, i can see 5 services up and running including SC self registered one.
After that when my microservice boots up, it can register itself with SC. And in the log i can see the unique service Id getting registered successfully. But in the SC UI the newly registered microservice is not showing up in the list.

Basically for understanding, it is not quite obvious from the documentation - What is the difference between platform and client side registration deployment mode of K8?

What could go wrong with platform registration mode which does not display newly registered service in the list?

Please help me understand!.

Thanks,
Meenakshi

@little-cui
Copy link
Member

After integrating with K8s, users only need to write K8s service (https://kubernetes.io/docs/concepts/services-networking/service/) and create it, it will be automatically synchronized to SC, and all components discovered through the client can be accessed K8s service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants