The issue tracker is ONLY used for the bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before you raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
BUG REPORT
Please describe the issue you observed:
What did you do (The steps to reproduce)?
used opertaor to deploy rocketmq cluster，stroageModel use stoargeClass，backend stoage is longhorn，the cluster is normal when first deploy ,but when I delete pod sometime or update configmap and restart pod ，the broker or nameserver restart failed，the log of broker no obvious mistakes。
What did you expect to see?
opeartor not support longhorn as backend stoage ? how to use?
Please tell us about your environment:
k8s： 1.21.7
operator： 0.3.0
rocketmq： 4.5
The issue tracker is ONLY used for the bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before you raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
BUG REPORT