Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
This is to handle cluster unregistration in the server side. This should be as simple as just deleting respective namespace for this cluster and that should take care of deleting anything inside that namespace.
What you expected to happen:
After unregistration, manager should not have any idea about the target cluster
How to reproduce it (as minimally and precisely as possible):
Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
What happened: This is to handle cluster unregistration in the server side. This should be as simple as just deleting respective namespace for this cluster and that should take care of deleting anything inside that namespace.
What you expected to happen: After unregistration, manager should not have any idea about the target cluster
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
$ kubectl logs