QQE-737 | Make Kafka use KRaft mode

[fedinskiy]

Summary

In KRaft mode Zookeper is not used, since brokers communicate to each other directly.

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[fedinskiy]

run tests

[michalvavrik]

I think it's alright. I'll need to re-check later today when I have more time and CI is green.

[michalvavrik]

@fedinskiy can you confirm you run smoke check on SASL_SSL and Kafka SSL scenarios in TS?

[fedinskiy]

I have run both Openshift and baremetal tests in framework in all three examples/kafka* nodules. I am running TS tests now

[fedinskiy]

Kafka SSL test in TS (messaging-kafka-ssl module) went just fine.

There is a failure in KafkaGratefulShutdownIT (will investigate it next week) and in Snappy tests (they read kafka logs manually, so we need to change the directory)

[michalvavrik]

Again, I think it's very good job, but let's wait till next week when you finish TS investigation. Changes LGTM.

[michalvavrik]

run tests

[michalvavrik]

run tests

[michalvavrik]

Failure of the OpenShiftS2iQuickstartUsingDefaultsIT in OCP native mode is not related. Let's improve in follow-up PR's if there are fixes required for TS.

[mjurc]

This also needs to be backported to the other supported branches too, since this also enables the now supported usage of Kafka in KRaft mode without deprecated Debezium.