apache
helm deployment operator deployment, uninstall cannot delete the replicaSet container, what is the solution?
After helm operator is installed, the replica can be deleted, but the pod container cannot be deleted. The reason is that the replicaSet cannot be deleted. After the next deployment, a new container is added. It is very distressing. Is there any solution? The new deployment will be in replicaSet+1 and cannot be deleted directly through helm uninstall.
kubectl get rs
rocketmq-operator-66c596bf54 1 1 1 5m3s rocketmq-operator-674f864b48 1 1 0 11m rocketmq-operator-c48db88cc 1 1 0 5m59s
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.
您的意思是操作员创建的 Pod 在运行后没有被删除吗
helm uninstall？实际上操作员避免了级联删除操作，这在生产中似乎是高风险的。 用户必须手动删除RocketMQ本身的pod。
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 the replicaSet cannot be deleted. As a result, after helm uninstall is executed, helm install will be executed again. +1 on a one-time basis, there will be 2 rocketmq operator container services. I am very distressed. I hope it can be solved, or is there any way to solve it?
Do you mean that the pods created by the operator are not deleted after running
helm uninstall? The operator actually avoids cascading delete operations, which seems to be high risk in production. Users must manually delete RocketMQ pods themselves.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 replicaset container services. Currently, they can only be deleted through the kubectl rs command, which is very distressing.
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
@xiaosong372089396 Pls also show the results of kubectl get deploy after running helm uninstall.