fix(role-instance): restart policy does not take effect#185
fix(role-instance): restart policy does not take effect#185cheyang merged 2 commits intosgl-project:mainfrom
Conversation
Summary of ChangesHello, 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 resolves an issue where the 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. Changelog
Activity
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.
Pull request overview
This PR fixes a bug (Issue #165) where setting RecreateInstanceOnPodRestart as the RestartPolicy on an Instance workload had no effect. The instance controller was not checking the restart policy, so when a pod failed or was deleted, the sibling pods in the same instance were not being recreated.
Changes:
- Introduces
shouldRecreateInstanceto check whether the instance should be fully recreated based onRestartPolicy=RecreateInstanceOnPodRestart, triggered either by container restarts or by pod count falling below expected. - Adds helper functions
wasInstanceReady(checksInstanceReadycondition in status) andgetExpectedPodCount(sums component sizes) to support the recreation decision. - Wires the
shouldRecreateInstancecheck intocalculateDiffsWithExpectationbefore the normal scale/update logic.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Code Review
This pull request implements the RecreateInstanceOnPodRestart policy for Instance resources. The core logic correctly identifies conditions for instance recreation (pod restarts or deletions) and triggers it by marking all existing pods for deletion. The implementation includes necessary checks to prevent infinite recreation loops, such as verifying the instance was previously in a Ready state before acting on pod deletions. I've found a potential compilation issue and a suggestion for a performance improvement.
Ⅰ. Motivation
Ⅱ. Modifications
Ⅲ. Does this pull request fix one issue?
fixes #165
Ⅳ. 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.