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

[Summer 2022] Nacos支持从K8S服务发现中同步服务元数据。 #8309

Closed
realJackSun opened this issue May 7, 2022 · 4 comments
Closed

[Summer 2022] Nacos支持从K8S服务发现中同步服务元数据。 #8309

realJackSun opened this issue May 7, 2022 · 4 comments
Labels
Summer

Comments

@realJackSun
Copy link
Collaborator

realJackSun commented May 7, 2022 •
edited
Loading

Nacos支持从K8S服务发现中同步服务元数据

Nacos支持实时感知K8S的服务上下线信息，并获取其服务元数据，并将这些信息同步到Nacos的CMDB模块。最终效果为，用户通过Nacos标签查询接口指定标签条件，即可查询到满足要求的实例列表。
@realJackSun realJackSun changed the title [Summer 2022] Pulling metadata from K8S and synchronizing it to the CMDB module. [Summer 2022] Nacos支持从K8S服务发现中同步服务元数据。 May 11, 2022
@xjlgod
Copy link

xjlgod commented May 11, 2022

您好，我是在校学生，去年也参加过summer2021并成功结题。我想问下此issue中的感知K8S的服务上下线信息，是指的用户选择Nacos中的服务，然后通过api-server的接口来查询这些服务元数据吗？谢谢您的回答。

@li-xiao-shuang
Copy link
Collaborator

您好，我是在校学生，去年也参加过summer2021并成功结题。我想问下此issue中的感知K8S的服务上下线信息，是指的用户选择Nacos中的服务，然后通过api-server的接口来查询这些服务元数据吗？谢谢您的回答。

可以通过开源之夏官网联系对应的导师沟通

@xjlgod
Copy link

xjlgod commented May 12, 2022

嗯嗯好的，谢谢您

@realJackSun realJackSun mentioned this issue Sep 13, 2022
Open
@EmanuelGi EmanuelGi mentioned this issue Sep 26, 2022
Merged
5 tasks
KomachiSion pushed a commit that referenced this issue Sep 29, 2022
@EmanuelGi
[ISSUE #8309] Sync services and endpoints from k8s (#9220)
3f3ea5e 
* [ISSUE#8309] Nacos supports synchronizing service metadata from k8s service discovery. (#7211)  * Synchronize k8s services.  * Synchronize k8s endpoints.

* ApiClient uses the default configuration instead

* Start registered Informers after registering handlers

* Compare oldServicePorts and newServicePorts to determine portChange

* Delete the logic of service renaming judgment

* Fix error in the process of registering instances

* Use independent log

* add k8s sync switch and start informer optimization

* start informer optimization
@stale
Copy link

stale bot commented Nov 12, 2022

Thanks for your feedback and contribution. But the issue/pull request has not had recent activity more than 180 days. This issue/pull request will be closed if no further activity occurs 7 days later.
We may solve this issue in new version. So can you upgrade to newest version and retry?
If there are still issues or want to contribute again. Please create new issue or pull request again.

@stale stale bot added the expired No active for a long time label Nov 12, 2022
@KomachiSion KomachiSion removed the expired No active for a long time label Jan 10, 2023
@KomachiSion KomachiSion closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2023
@KomachiSion KomachiSion added Summer and removed Summer labels Apr 10, 2023
@KomachiSion KomachiSion mentioned this issue Jul 11, 2023
Merged
5 tasks
wukong121 pushed a commit to wukong121/nacos that referenced this issue Aug 4, 2023
@EmanuelGi @wukong121
[ISSUE alibaba#8309] Sync services and endpoints from k8s (alibaba#9220)
1f8caa0 
* [ISSUE#8309] Nacos supports synchronizing service metadata from k8s service discovery. (alibaba#7211)  * Synchronize k8s services.  * Synchronize k8s endpoints.

* ApiClient uses the default configuration instead

* Start registered Informers after registering handlers

* Compare oldServicePorts and newServicePorts to determine portChange

* Delete the logic of service renaming judgment

* Fix error in the process of registering instances

* Use independent log

* add k8s sync switch and start informer optimization

* start informer optimization
wukong121 pushed a commit to wukong121/nacos that referenced this issue Aug 4, 2023
@EmanuelGi @wukong121
[ISSUE alibaba#8309] Sync services and endpoints from k8s (alibaba#9220)
96e9490 
* [ISSUE#8309] Nacos supports synchronizing service metadata from k8s service discovery. (alibaba#7211)  * Synchronize k8s services.  * Synchronize k8s endpoints.

* ApiClient uses the default configuration instead

* Start registered Informers after registering handlers

* Compare oldServicePorts and newServicePorts to determine portChange

* Delete the logic of service renaming judgment

* Fix error in the process of registering instances

* Use independent log

* add k8s sync switch and start informer optimization

* start informer optimization
@Sussmann1368 Sussmann1368 mentioned this issue Dec 11, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Summer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@li-xiao-shuang @KomachiSion @xjlgod @realJackSun