separate logging facilities

These logs here should be all more considered as debug logs

time="2018-09-10T07:24:35Z" level=info msg="Updating Deployment default/cluster-registry-master-82 for StackSet stack default/cluster-registry-master-82" controller=stacks namespace=default stackset=cluster-registry
time="2018-09-10T07:24:35Z" level=info msg="Updating Deployment default/cluster-registry-master-79 for StackSet stack default/cluster-registry-master-79" controller=stacks namespace=default stackset=cluster-registry
time="2018-09-10T07:24:35Z" level=info msg="Updating Deployment default/cluster-registry-master-80 for StackSet stack default/cluster-registry-master-80" controller=stacks namespace=default stackset=cluster-registry
time="2018-09-10T07:24:35Z" level=info msg="Updating Deployment default/cluster-registry-master-81 for StackSet stack default/cluster-registry-master-81" controller=stacks namespace=default stackset=cluster-registry
time="2018-09-10T07:24:45Z" level=info msg="Updating Deployment default/cluster-registry-master-79 for StackSet stack default/cluster-registry-master-79" controller=stacks namespace=default stackset=cluster-registry

This is more client-go library internal noise.

ERROR: logging before flag.Parse: E0910 07:24:31.764057       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)

Start by tracing the stack controller logs identified by controller=stacks, then inspect the client-go streamwatcher.go:109 message shown in the report. Determine how the two sources can use separate logging facilities and verify that routine controller updates and client-go internal noise are no longer emitted at info or error severity.