Currently there is no way to check if a cluster has been drained successfully and workload has been moved completely.

[kasturinarra]

Describe the bug Currently there is no way for user to check if a cluster has been drained successfully and workload has been moved completely to another synctarget

[knarra@knarra ~]$ kubectl version -o yaml clientVersion: buildDate: "2022-07-29T17:25:01Z" compiler: gc gitCommit: 70750898e45ff4a349995b08e1d64a359e4c4880 gitTreeState: clean gitVersion: v1.24.1 goVersion: go1.18.4 major: "1" minor: "24" platform: linux/amd64 kustomizeVersion: v4.5.4 serverVersion: buildDate: "2022-08-02T22:50:38Z" compiler: gc gitCommit: 350f7e9 gitTreeState: dirty gitVersion: v1.24.3+kcp-v0.0.0-350f7e9 goVersion: go1.17.13 major: "1" minor: "24" platform: linux/amd64

To Reproduce Steps to reproduce the behavior:

1. Add a synctarget by running the command ‘kubectl kcp workload sync knarracluster1 --syncer-image ghcr.io/kcp-dev/kcp/syncer:cf540bb -o - | KUBECONFIG=/home/knarra/Downloads/kubeconfig_411 kubectl apply -f -’
2. Create deployment using the command ‘kubectl create deployment kuard --image gcr.io/kuar-demo/kuard-amd64:blue --dry-run=client -o yaml > kuard.yaml & kubectl apply -f kuard.yaml`
3. Now make sure that deployment has been successfully synced
4. Run command ‘kubectl kcp workload drain knarracluster1`
5. There is no user facing message which indicates that the cluster has been actually drained and all the workload has been moved.

Expected behavior There should be a way for user to check if cluster has been drained and all the workload has been moved successfully.

Additional context Add any other context about the problem here.

[mjudeikis]

/transfer-issue contrib-tmc