Move heapster/cadvisor resources into their own project

[fejta]

Move heapster/cadvisor resources into their own project

[fejta]

But first we need to address #189

[fejta]

Jeff what's left to do here?

[ixdy]

Someone needs to look at the tests and see if they are creating any resources in GCP (and if so, make sure they're using their own projects).

[ixdy]

Yeah, this is still not fixed. We have special snowflake e2e-cadvisor VMs in both kubernetes-jenkins and kubernetes-jenkins-pull which probably need to be migrated to their own projects.
cc @timstclair @vishh

[fejta]

/assign @timstclair @vishh @ixdy

Will the three of be able to resolve this during the 1.7 timeframe?

Otherwise I woud like to delete these VMs and jobs in July.

[fejta]

We should delete these VMs soon. Left a notice on kubernetes-retired/heapster#1773 to move these jobs to a different project

[krzyzacy]

cc @dashpole cadvisor also still have a Jenkins VM, while we are going to kill Jenkins soon

[fejta]

Will delete these jobs as soon as we're out of 1.9 freeze

[BenTheElder]

re-ping @dashpole for cadvisor jobs deletion warning ^

[BenTheElder]

@dashpole and I discussed this today. I will assist him with looking at migrating cadvisor to Prow soonish, nobody wants to run a jenkins cluster :+)
When we do we will see if it is possible to move the heapster jobs in the same fashion.

[krzyzacy]

/assign
/assign @BenTheElder @dashpole

[krzyzacy]

kubernetes-jenkins is wiped and I'll close this

(this is the oldest open issue in test-infra, /shrug)

[BenTheElder]

Cadvisor at least definitely has their resources in their own project now as well (@dashpole owns this)

…

On Wed, Feb 7, 2018 at 3:04 PM, Sen Lu ***@***.***> wrote: kubernetes-jenkins is wiped and I'll close this — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#190 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA4Bqx8L54mnWGccqXktAeTRou-PG_4lks5tSiwagaJpZM4I42h8> .