Collect apiserver and cadvisor metrics from master instance
Collect apiserver and cadvisor metrics from master instance

use master ip directly for now instead of kubectl-proxy

kubernetes services is 443 only, let's see if removing the indirection
changes things too much, otherwise we'll drop back to trying to proxy
the master ip directly

Curious if nginx is going to act differently with prometheus polling it
instead of the apiserver directly.  This likely won't work with N
apiservers behind nginx, I expect we'll get competing metrics.

Will need to hack in similar functionality to -K to discover the pool of
apiservers to scrape.  Might be time to reinvestigate service discovery,
prometheus has better support than what we're using right now.

mikeln/kraken-services,mikeln/kraken-services,mikeln/kraken-services,Samsung-AG/kraken-services,maratoid/kraken-services,Samsung-AG/kraken-services,Samsung-AG/kraken-services,Samsung-AG/kraken-services,maratoid/kraken-services,mikeln/kraken-services,Samsung-AG/kraken-services,maratoid/kraken-services,mikeln/kraken-services,maratoid/kraken-services,Samsung-AG/kraken-services,mikeln/kraken-services,maratoid/kraken-services,maratoid/kraken-services