What happened:
At the very first, it kind of looked like we don't need to have controller for the cluster management as it is pretty much storing the info in etcD which can be done using CRD. But, we might want to use the controller to verify whether manager can connect to target cluster, refresh the service account token and some minimal health check in a regular frequency
What you expected to happen:
Controller should listen to the cluster events and keep update the status
How to reproduce it (as minimally and precisely as possible):
Is this a BUG REPORT or FEATURE REQUEST?: SUBTASK
What happened: At the very first, it kind of looked like we don't need to have controller for the cluster management as it is pretty much storing the info in etcD which can be done using CRD. But, we might want to use the controller to verify whether manager can connect to target cluster, refresh the service account token and some minimal health check in a regular frequency
What you expected to happen: Controller should listen to the cluster events and keep update the status
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
$ kubectl logs