[ISSUE #8309] Sync services and endpoints from k8s #9220
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ervice discovery. (alibaba#7211) * Synchronize k8s services. * Synchronize k8s endpoints.
|
|
pixystone
approved these changes
Sep 29, 2022
| @@ -702,6 +719,11 @@ | |||
| <level value="DEBUG"/> | |||
| <appender-ref ref="core-auth"/> | |||
| </logger> | |||
|
|
|||
| <logger name="com.alibaba.nacos.k8s.sync.main" additivity="false"> | |||
| <level value="DEBUG"/> | |||
There was a problem hiding this comment.
That'd be better defaults INFO .
KomachiSion
approved these changes
Sep 29, 2022
wukong121
pushed a commit
to wukong121/nacos
that referenced
this pull request
Aug 4, 2023
* [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 pull request
Aug 4, 2023
* [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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please do not create a Pull Request without creating an issue first.
What is the purpose of the change
For issue #8309
Brief changelog
Sync services and endpoints from k8s.
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily:
[ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=trueto make sure basic checks pass. Runmvn clean install -DskipITsto make sure unit-test pass. Runmvn clean test-compile failsafe:integration-testto make sure integration-test pass.