Skip to content

[Bugfix] Wait for the OME controller Pod to become ready#228

Merged
slin1237 merged 1 commit into
ome-projects:mainfrom
JiangJiaWei1103:wait-for-ome-controller-pod
Aug 4, 2025
Merged

[Bugfix] Wait for the OME controller Pod to become ready#228
slin1237 merged 1 commit into
ome-projects:mainfrom
JiangJiaWei1103:wait-for-ome-controller-pod

Conversation

@JiangJiaWei1103
Copy link
Copy Markdown
Contributor

What type of PR is this?

/kind bug

What this PR does / why we need it:

We set WAIT_FOR_CONTROLLER to true by default to ensure the OME controller Pod is ready before ome-webhook-server-service is invoked. This helps prevent connection errors during installation.

Which issue(s) this PR fixes:

Fixes #225

Special notes for your reviewer:

N/A

Does this PR introduce a user-facing change?

NONE

Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a 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 @JiangJiaWei1103, 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!

I've implemented a bugfix to resolve an issue where the OME controller Pod might not be fully ready when other services attempt to interact with it, leading to connection errors during the installation process. The core of this change involves setting a default configuration to explicitly wait for the controller's readiness, thereby ensuring a more robust and error-free installation experience.

Highlights

  • OME Controller Readiness: I've updated the default configuration to ensure that the OME controller Pod is ready before the ome-webhook-server-service is invoked. This change directly addresses and prevents connection errors that could occur during installation.
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 or fill out our survey to provide feedback.

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

  1. 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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a 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 addresses a race condition during installation by ensuring the OME controller Pod is ready before other resources are applied. The change in the Makefile to set WAIT_FOR_CONTROLLER to true by default is a good and robust solution to prevent potential connection errors with the webhook server. The change is correct and well-contained. I have no further suggestions.

@JiangJiaWei1103
Copy link
Copy Markdown
Contributor Author

@slin1237 PTAL, thanks!

@slin1237
Copy link
Copy Markdown
Collaborator

slin1237 commented Aug 4, 2025

thanks for the fix

@slin1237 slin1237 merged commit 3d2e8fd into ome-projects:main Aug 4, 2025
24 checks passed
slin1237 pushed a commit that referenced this pull request Dec 22, 2025
fix: Wait for the OME controller Pod to become ready

Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[SUPPORT] Failed to call webhook when applying cluster resources

2 participants