Lari Hotari

@dlg99 please address the review feedback, https://github.com/apache/pulsar/pull/23380#pullrequestreview-2339343482.

Closing and reopening to see if it triggers CI since the GitHub Actions workflow hasn't been run.

> Hi @lhotari, we would like to you OIDC support too, can someone review this PR ? Thank you @gulecroc @brunodomenici Yes, OIDC support would be very useful. We'd also...

> One possibility would be to have a lightweight OIDC provider get deployed in the kind cluster that the CI jobs use for validation. Keycloak could be one choice. ClaudeAI...

@brunodomenici @gulecroc In addition to plain OIDC provider support, there would be a need to handle broker-to-broker and proxy-to-broker authentication. The foundations for this is described in the Pulsar docs...

> Thank you @lhotari, I start working with @brunodomenici on your reviews @gulecroc Sounds good. The Bitnami Keycloak chart could be used in CI to install Keycloak, https://github.com/bitnami/charts/tree/main/bitnami/keycloak . It...

@merlimat license check fails

@hamadodene It would be helpful to share Pulsar version & Bookkeeper version & possible customized Ensemble size (E), write quorum (Qw) and ack quorum (Qa) size.

@hamadodene noticed this in the output that you shared: > jute.maxbuffer value is 1048575 Bytes in Pulsar, the default is `-Djute.maxbuffer=10485760`. When you run Bookkeeper, do you use `bin/pulsar bookie`...

When running Bookkeeper with Pulsar's `bin/pulsar bookie` script, one of the main differences is that Bookkeeper will use [`org.apache.pulsar.metadata.bookkeeper.PulsarMetadataBookieDriver`](https://github.com/apache/pulsar/blob/master/pulsar-metadata/src/main/java/org/apache/pulsar/metadata/bookkeeper/PulsarMetadataBookieDriver.java) and [`org.apache.pulsar.metadata.bookkeeper.PulsarMetadataClientDriver`](https://github.com/apache/pulsar/blob/master/pulsar-metadata/src/main/java/org/apache/pulsar/metadata/bookkeeper/PulsarMetadataClientDriver.java) from the Pulsar code base for metadata operations.