Skip to content

Conversation

@kabir
Copy link
Collaborator

@kabir kabir commented Oct 28, 2025

Add SKIP_ENTITY_OPERATOR_WAIT environment variable to work around entity operator timeout issues in some environments (Linux + Podman).

When set to 'true':

  • Checks only Kafka broker pod readiness (not full Kafka resource)
  • Polls Kafka broker directly to verify topic creation

This is an opt-in workaround that doesn't affect standard deployments.

Also improves user messaging:

  • Added timeout information (10 minutes)
  • Added proactive hints about workaround if timeout occurs
  • Set expectations for topic creation timing

Add SKIP_ENTITY_OPERATOR_WAIT environment variable to work around
entity operator timeout issues in some environments (Linux + Podman).

When set to 'true':
- Checks only Kafka broker pod readiness (not full Kafka resource)
- Polls Kafka broker directly to verify topic creation

This is an opt-in workaround that doesn't affect standard deployments.

Also improves user messaging:
- Added timeout information (10 minutes)
- Added proactive hints about workaround if timeout occurs
- Set expectations for topic creation timing
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @kabir, 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 introduces an optional workaround for Kafka entity operator timeout issues that can occur in specific environments, particularly when using Kind with Podman on Linux. By setting a new environment variable, users can opt to skip the full entity operator readiness checks, allowing the deployment to proceed by verifying only the core Kafka broker and directly confirming topic creation. This change also significantly improves user experience by providing better guidance and troubleshooting tips within the deployment process and documentation.

Highlights

  • New Environment Variable for Kafka Deployment: Introduces SKIP_ENTITY_OPERATOR_WAIT to bypass entity operator readiness checks, specifically for Kind deployments with Podman on Linux, addressing potential timeout issues.
  • Streamlined Kafka Readiness Checks: When SKIP_ENTITY_OPERATOR_WAIT is enabled, the deployment script now only verifies the Kafka broker pod's readiness and directly polls the broker for topic creation, rather than waiting for the full Kafka resource or topic operator.
  • Enhanced User Guidance: The deploy.sh script and README.md have been updated with clearer messaging, including explicit timeout information (10 minutes) and proactive troubleshooting hints for entity operator timeouts.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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

  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
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 introduces a valuable workaround for Kafka entity operator timeouts in certain environments by adding the SKIP_ENTITY_OPERATOR_WAIT flag. The changes are well-implemented in the deployment script and clearly documented in the README. My review includes one suggestion to improve the error handling in the deployment script for a better user experience when timeouts occur.

@fjuma fjuma merged commit 85dd747 into a2aproject:main Oct 28, 2025
9 of 12 checks passed
@kabir kabir deleted the event-queues-replicated-example-kind branch November 3, 2025 13:01
kabir added a commit to kabir/a2a-java that referenced this pull request Dec 23, 2025
Add SKIP_ENTITY_OPERATOR_WAIT environment variable to work around entity
operator timeout issues in some environments (Linux + Podman).

When set to 'true':
- Checks only Kafka broker pod readiness (not full Kafka resource)
- Polls Kafka broker directly to verify topic creation

This is an opt-in workaround that doesn't affect standard deployments.

Also improves user messaging:
- Added timeout information (10 minutes)
- Added proactive hints about workaround if timeout occurs
- Set expectations for topic creation timing
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.

2 participants