Fix Kafka setup by ensuring Strimzi CRDs are established before applying resources#6602
Closed
anandyadav3559 wants to merge 1 commit intoapache:mainfrom
Closed
Fix Kafka setup by ensuring Strimzi CRDs are established before applying resources#6602anandyadav3559 wants to merge 1 commit intoapache:mainfrom
anandyadav3559 wants to merge 1 commit intoapache:mainfrom
Conversation
… Kafka resources Kafka setup fails with errors like 'no matches for kind KafkaNodePool' because Strimzi CRDs are not fully established when Kafka resources are applied. Added explicit waits for CRDs and operator readiness to prevent race condition. Also updated KEDA installation to use server-side apply to avoid annotation size issues.
squakez
reviewed
May 4, 2026
Contributor
squakez
left a comment
squakez
left a comment
There was a problem hiding this comment.
Thanks for the root cause analysis and the attempt to fix. We need also to update the duck type which we use internally: https://github.com/apache/camel-k/tree/main/pkg/apis/duck/strimzi/v1beta2
Contributor
Author
|
I'll see to it and update it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes: #6596
The Kafka setup fails with errors like:
"no matches for kind KafkaNodePool in version kafka.strimzi.io/v1beta2"
Although Strimzi CRDs are installed, they are not fully established when Kafka resources are applied. This creates a race condition where Kubernetes does not yet recognize the resource types.
This PR adds explicit waits to ensure CRDs are established before applying Kafka resources.
Additionally, KEDA installation is updated to use server-side apply to avoid annotation size issues.