sinloss opened a new issue, #196:
URL: https://github.com/apache/rocketmq-operator/issues/196

   **BUG REPORT**
   
   When trying to deploy the `rocketmq-operator` using the 
[chart](https://github.com/apache/rocketmq-operator/tree/master/charts/rocketmq-operator)
 , though rare, user may want to assign a different name for the 
`serviceAccountName` <sup>*1.1*</sup>. In those cases, the helm chart is 
expected to work properly<sup>*1.2*</sup>. Yet in the current configuration, 
use could run into an error saying **serviceaccount "rocketmq-operator" not 
found**<sup>*1.3*</sup>.
   
   This issue was first encountered on a self-hosted `Kubernetes v1.25.4` 
cluster with `2` nodes. The deployment was created using `Helm 
version.BuildInfo{Version:"v3.12.0", 
GitCommit:"c9f554d75773799f72ceef38c51210f1842a1dea", GitTreeState:"clean", 
GoVersion:"go1.20.3"}`.
   
   The root of this issue is that on one hand in the 
[operator.yaml](https://github.com/apache/rocketmq-operator/blob/a8665716c8028741ec106814798e39fe07e6dcaa/charts/rocketmq-operator/templates/operator.yaml#L30)
 the `serviceAccountName` is expected to be `rocketmq-operator`, on the other 
hand in the 
[role_binding.yaml](https://github.com/apache/rocketmq-operator/blob/a8665716c8028741ec106814798e39fe07e6dcaa/charts/rocketmq-operator/templates/role_binding.yaml#L27C11-L27C66)
 and the 
[service_account.yaml](https://github.com/apache/rocketmq-operator/blob/a8665716c8028741ec106814798e39fe07e6dcaa/charts/rocketmq-operator/templates/service_account.yaml#L19)
 the `serviceAccountName` is expected to be `{{ template 
"rocketmq-operator.serviceAccountName" . }}`. Hence, the `{{ template 
"rocketmq-operator.serviceAccountName" . }}` could produce names the 
`operator.yaml` will never acknowledge.
   
   ---
   *1.1* What did you do (The steps to reproduce)?
   *1.2* What did you expect to see?
   *1.3* What did you see instead?


-- 
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: commits-unsubscr...@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to