Awsmsniper commented on issue #447:
URL: 
https://github.com/apache/pulsar-helm-chart/issues/447#issuecomment-1912391114

   > > > have you tested with the default image which is `3.0.2`? (remove 
`defaultPulsarImageTag`)
   > > 
   > > 
   > > No, I am using version 3.1.1, which defaults to version 3.1.1
   > 
   > Pulsar 3.1.1 版本中存在一个错误。它在 Pulsar 的 3.0.2 和 3.1.2 版本中已修复。这是这个修复程序: 
[apache/pulsar#21428](https://github.com/apache/pulsar/pull/21428) 。在 
branch-3.0 
中提交:[apache/pulsar@df4b0d8f](https://github.com/apache/pulsar/commit/df4b0d8f)(包含在
 3.0.2 中)和 
branch-3.1:[apache/pulsar@1496925f](https://github.com/apache/pulsar/commit/1496925f)(包含在
 3.1.2 中)。
   > 
   > CI 测试使用 Pulsar 3.0.2 
镜像运行。我也运行了测试,没有出现问题。https://github.com/lhotari/pulsar-helm-chart/actions/runs/7670897358?pr=7`defaultPulsarImageTag:
 3.1.2`
   > 
   > 请使用 Pulsar 3.0.2 或 3.1.2 来获取修复程序。
   
   Thank you for your reply. Could you please take a look at the configuration 
of jwt in your values. yaml? Here is my configuration, is there any error?
   
   ```yaml
   # uses chart's appVersion when unspecified
   defaultPulsarImageTag: 3.1.2
   
   auth:
     authentication:
       enabled: true
       provider: "jwt"
       jwt:
         # Enable JWT authentication
         # If the token is generated by a secret key, set the usingSecretKey as 
true.
         # If the token is generated by a private key, set the usingSecretKey 
as false.
         usingSecretKey: false
     authorization:
       enabled: true
     superUsers:
       # broker to broker communication
       broker: "broker-admin"
       # proxy to broker communication
       proxy: "proxy-admin"
       # pulsar-admin client to broker/proxy communication
       client: "admin"
     # omits the above proxy role from superusers on the proxy
     # and configures it as a proxy role on the broker in addition to the 
superusers
     useProxyRoles: true
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to