rabbitmq/messaging-topology-operator

Remove topology objects from "all" category

Zerpet opened this issue · 1 comments

All topology objects are part of the all category (see kubectl categories). This significantly slows down kubectl when a user runs kubectl get all. I don't think most users want to get rabbit related objects when they kubectl get all, neither appreciate the slowdown imposed by adding all topology resources to the all category.

I propose to remove all topology objects from all category, and keep the rabbitmq category.

This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring.