fix: use GetWorkloadName for instance address generation#138
fix: use GetWorkloadName for instance address generation#138Syspretor merged 1 commit intosgl-project:mainfrom
Conversation
Summary of ChangesHello @bcfre, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an issue in the system's instance address generation. It refines how individual service instances are named and located by ensuring that a dedicated helper function is used to derive the correct workload name. This modification is critical for maintaining accurate service discovery and overall system stability, preventing potential misconfigurations or communication failures. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly fixes the instance address generation to use the full workload name, which is necessary for creating resolvable pod DNS names. However, the PR is incomplete because the unit tests have not been updated to reflect this change, which will cause the build to fail. Please update the tests in pkg/discovery/config_builder_test.go.
There was a problem hiding this comment.
Pull request overview
This PR fixes a bug in instance address generation to use the full workload name (combining RoleBasedGroup name and role name) instead of just the role name. This ensures that the generated addresses correctly match the actual pod names created by the workload controllers.
Changes:
- Updated
buildInstancesmethod to useGetWorkloadName(role)instead ofrole.Namefor instance address generation
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: 柏存 <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
/lgtm |
Ⅰ. Motivation
before
after
actual pod template
Ⅱ. Modifications
Ⅲ. Does this pull request fix one issue?
fixes #XXXX
Ⅳ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅴ. Describe how to verify it
VI. Special notes for reviews
Checklist
make fmt.