-
Notifications
You must be signed in to change notification settings - Fork 379
feat(webhook): Add additional check for initContainers #1278
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mayooot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @mayooot, 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 PR extends the webhook logic to include initContainers when performing resource and scheduler assignment checks. Previously, these checks were only applied to standard containers. This ensures a more comprehensive validation process for pods.
Highlights
- Webhook Logic Enhancement: The webhook's validation process has been updated to iterate over both standard containers and initContainers when checking resources and scheduler assignments.
- Logging Improvement: An existing informational log message has been modified to provide clearer context, indicating that resource and scheduler assignment checks are being performed.
Using Gemini Code Assist
The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
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 .gemini/
folder in the base of the repository. Detailed instructions can be found here.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
36dd6db
to
0be56b2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request extends the webhook's resource checking to include initContainers. The implementation has a critical bug that will cause a panic due to an out-of-bounds index access when iterating over the containers. I've provided a fix that correctly and safely iterates over both regular and init containers while ensuring that any mutations are applied to the original pod specification.
Codecov Report❌ Patch coverage is
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
Is this work for initContainer? have you tested on your environment? |
Signed-off-by: Harry Li <[email protected]>
0be56b2
to
57a634f
Compare
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request adds a check for initContainers
in the admission webhook, mirroring the existing logic for regular containers. My review focuses on improving code maintainability by refactoring duplicated logic and addressing a variable shadowing issue in the new test case. These changes will make the code cleaner and less prone to errors.
I'll test this case in my k3s once I have prepared the HAMi development environment. |
13c0db6
to
4fbbc5f
Compare
Signed-off-by: Harry Li <[email protected]>
4fbbc5f
to
b29fec7
Compare
CC @Shouren |
cc @s |
@mayooot @archlitchi Let me test it later. |
@mayooot @archlitchi I have tested this PR in my environment with two cases:
Both cases failed. After checking the code, i found that |
What type of PR is this?
Add one of the following kinds:
/kind cleanup
/kind feature
What this PR does / why we need it:
Add additional check for initContainers in webhook