xiaosong372089396 commented on issue #187: URL: https://github.com/apache/rocketmq-operator/issues/187#issuecomment-1769681524
> Did you mean the pods created by the operator were not removed after running `helm uninstall`? Actually the operator avoids the cascading delete operations, which seems to be high-risk in production. Users have to delete pods of RocketMQ itself manually. No, the reason is that the rocketmq Operator service installed through helm install runs normally, but the rocketmq Operator container pod cannot be deleted through helm uninstall. The reason is that the rocketmq operator container in replicaSet cannot be deleted. As a result, after helm uninstall is executed, helm install will be executed again. One time +1, there will be 2 rocketmq operator container services. I am very troubled. Hope it can be solved, or is there any way to solve it? kubectl get rs Rocketmq-operator-66c596bf54 1 1 1 5m3s Rocketmq-operator-674f864b48 1 1 0 11m Rocketmq-operator-c48db88cc 1 1 0 5m59s There are multiple replica -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
