gulecroc

Hi @lhotari, For the moment I have configure the authentication : * added bitnami keycloak chart as dependency with default value `keycloak.enabled: false` * import Datastax `pulsar-realm.json` on keycloak startup...

Futhermore, if I propagate the auth from proxy to broker : * proxy conf : ```yaml forwardAuthorizationCredentials: "true" ``` * broker conf : ```yaml authenticateOriginalAuthData: "true" ``` The client is...

I have done the test with one role in the client token, so I expect the same behavior with the 2 authorization providers `org.apache.pulsar.broker.authorization.PulsarAuthorizationProvider` and `org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider`

Workaround : I create a fake service so kube-vip can update iptables with IP and port SNAT : ```yaml --- apiVersion: v1 kind: Service metadata: annotations: kube-vip.io/egress: "true" kube-vip.io/egress-destination-ports: tcp:389...

Hi @skanakal , is it possible to move this issue to fleet project ? Thank you