client-go: glog terminates program when it can't create a logfile

This is quite a big deal when using with containerized read-only environments. We should absolutely get rid of glog as it just calls os.Exit(2) if it can’t create a file, killing our entire process.

A workaround would be to do all calls to glog inside a seperate process, which shouldn’t be worth the hassle.