Cluster Operator for Kubernetes removal

769 views
Skip to first unread message

Norbert Egger

unread,
Feb 8, 2022, 10:41:00 AM2/8/22
to rabbitmq-users
Hi all,

i have deleted a RabbitMQ Cluster Operator with the command `kubectl delete -f cluster-operator.yml`

it looks like it has been removed, but when i check the secrets, there is still a rabbitmq-token-xxxx secret init. If i delete this secret, it gets recreated. The Secret has ca.crt, namespace and token as data in it. It is annotated with:
kubernetes.io/service-account.uid: 387a6777-9e4b-4db0-affc-763f8446d238

How can i make sure, that every part of the Cluster Operator was removed?

Thanks and best regards
Norbert
Message has been deleted

Norbert Egger

unread,
Jun 15, 2022, 3:50:00 AM6/15/22
to rabbitmq-users

Hi all,

i still have the problem, that the token gets recreated. Maybe you can suggest me an better place, where to put this issue to get it resolved?

best regards
Norbert

Michal Kuratczyk

unread,
Jun 15, 2022, 5:52:10 AM6/15/22
to rabbitm...@googlegroups.com
Hi,

These secrets are created by Kubernetes, not explicitly by the Operator deployment. If you have successfully deleted all your RabbitMQ Clusters and the Operator itself, and this secret still gets recreated,
then it's a Kubernetes question/issue. Do you still have the `rabbitmq-system` namespace after `kubectl delete -f cluster-operator.yaml`? Is that the namespace where you see the secret?

Best,

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/8a92a80c-de3c-46a1-8aba-532ac2206c8cn%40googlegroups.com.


--
Michał
RabbitMQ team
Reply all
Reply to author
Forward
0 new messages