Open
Conversation
Signed-off-by: Keith Wall <kwall@apache.org> Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
k-wall
force-pushed
the
strimzi-v1-migration
branch
from
ef945c9 to
83e5b2c
Compare
ppatierno
reviewed
Apr 8, 2026
|
DIscussed at the community call on 8 April. Atendees broadly supportive of the approach. Please review the proposal in some more detail and approve if happy. |
tombentley
approved these changes
Apr 8, 2026
Member
tombentley
left a comment
tombentley
left a comment
There was a problem hiding this comment.
Thanks Keith.
I generally am not in favour of changes which break compatibility. However in this case of a relatively new feature, which is unlikely to be in use in production (lacking TLS support), and with an easy workaround which comes without loss of functionality, I think it's justifiable.
ppatierno
approved these changes
Apr 9, 2026
Member
Author
|
This is what we see if the Kroxylicious is expecting v1beta2 while ther API server isn't serving it. |
Signed-off-by: Keith Wall <kwall@apache.org>
k-wall
force-pushed
the
strimzi-v1-migration
branch
from
7300bee to
d191a3d
Compare
k-wall
commented
Apr 9, 2026
|
|
||
| Currently, the Kroxylicious Operator will break when Strimzi 1.0.0 is released, as it will no longer be able to read `Kafka` resources at the `v1beta2` API version. | ||
|
|
||
| The Kroxylicious Operator must be updated to support Strimzi 1.0.0 and beyond. If this is not done, the Kroxylicious integration with Strimzi will cease to work. |
Member
Author
There was a problem hiding this comment.
Suggested change
| The Kroxylicious Operator must be updated to support Strimzi 1.0.0 and beyond. If this is not done, the Kroxylicious integration with Strimzi will cease to work. | |
| The Kroxylicious Operator must be updated to support Strimzi 1.0.0 and beyond. If this is not done, the Operator will fail completely when Strimzi CRDs are present without v1beta2 support. It will fail at startup. It uses the existence of the API group `kafka.strimzi.io` to determine if Strimzi is present (which will pass), but then the Informer will fail because the `/apis/kafka.strimzi.io/v1beta2/kafkas` endpoint will return an error). It is sufficient to cause the Operator to crash. |
Member
Author
There was a problem hiding this comment.
I've updated the proposal based on experimentation.
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
4 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.
Kroxylicious has a Strimzi integration feature that references the Kafka CR to automatically configure the upstream. This feature currently relies on the Strimzi's v1beta2 API. Strimzi is in the process of phasing out support for v1beta2, in favour of a new v1 API.
This proposal describes a way that the Kroxylicious operator may be changed to use the v1 API.