Don't hardcode 'ves-system' namespace in vp-manager
It's currently not possible to have more than one instance of 'ves' running in a cluster.
The root issue is the namespace 'ves-system' is hardcoded in vp-manager-0 during bootstrapping tasks. This is a poor practice and limits possible use cases. Note the log message below despite the fact that all ves resources were deployed to an arbitrary namespace:
Status:"Failure", Message:"services is forbidden: User \"system:serviceaccount:ves-system-1:vpm-sa\" cannot create resource \"services\" in API group \"\" in the namespace \"ves-system\"", Reason:"Forbidden", Details:(*v1.StatusDetails)(0xc000fd7200), Code:403}}