show differences between k8s-cluster and master branch

[stavalfi]

scenario:

if the k8s-cluster is out of sync with the master branch, it maybe because
someone is manually manage the deployments in the k8s-cluster.
he probably has a good reason to. maybe revert a deployment due to a bug in production.
to make sure that other merges of PRs won't bring back the bug of one of the micro-services,
we need to make sure that only changed packages in the current flow can be deployed.

problem:

k8s-cluster and master branch are out of sync

proposed feature:

show the diffrences between them.

possible solutions/hints:

1. every change of a deployment from the ci, will modify a label in k8s-eployment that say which git-revision is this deployment came from. later on, we can check what is the revision of origin/master and see which deployments doesn't have this revision in their label.