I was planning to tackle this one and in the process try to find a good Go replacement for calling external gcloud as part of the tests...

Will assign it to myself and see if I can get close to a proof of concept by end of this week or beginning of the next...

I have some pieces of monitoring.sh written in go as part of an integration
test I had developed for heapster. The code is in the heapster repo :
https://github.com/GoogleCloudPlatform/heapster/blob/master/integration/kube_test.go

Filipe I am happy to collaborate with you if that would help!

I think one option for this test is actually to just ENABLE_CLUSTER_MONITORING=true the e2e cluster and then use the default pods. Then it becomes somewhat similar to TestClusterDns in that it's testing the system pod setup, too.

+1 to that approach. That will test the cluster initialization logic as
well.

On Thu, Feb 5, 2015 at 1:21 PM, Zach Loafman notifications@github.com
wrote:

I think one option for this test is actually to just
ENABLE_CLUSTER_MONITORING=true the e2e cluster and then use the default
pods. Then it becomes somewhat similar to TestClusterDns in that it's
testing the system pod setup, too.

—
Reply to this email directly or view it on GitHub
#4186 (comment)
.

@filbranden: Any progress to report here? I was looking at items to include in tomorrow's Fix-It and this came up.

@filbranden: I can work on this one if you are busy.

@vishh @zmerlynn Feel free to take over or use it in tomorrow's Fix-It, thanks for the offer and sorry for hogging it for a while!

Assigned the issue to me. I might not get to this by tomorrow. So I will remove the "Fix-It" milestone for now.

@vishh Any update on this one?

Haven't gotten to this one yet.

On Mon, Mar 2, 2015 at 3:32 PM, Jeff Grafton notifications@github.com
wrote:

@vishh https://github.com/vishh Any update on this one?

—
Reply to this email directly or view it on GitHub
#4186 (comment)
.