Remove unused GCE disks #10

New Issue

raucao · 2019-01-02T04:41:14Z

raucao commented

2019-01-02 04:41:14 +00:00

Apparently they're not automatically deleted:

https://console.cloud.google.com/compute/disks?organizationId=772167872692&project=fluted-magpie-218106&diskssize=50

Apparently they're not automatically deleted: <https://console.cloud.google.com/compute/disks?organizationId=772167872692&project=fluted-magpie-218106&diskssize=50>

raucao changed title from ~~Clean old GCE disks~~ to Remove unused GCE disks

2019-01-02 04:41:38 +00:00

raucao commented

2019-03-04 06:09:22 +00:00

I removed the disks that weren't in use at all. But those were only 4 1GB ones. However, there are 3 100GB ones in use, and I have no idea what app/deployment using them (except that it's Kubernetes).

Also, there are 4 10GB disks in use by something called tk-vagrant-main-ubuntu-1404-23cee4, which I have no idea what it could be (that one's not Kubernetes).

@gregkare Any idea what's going on there?

I removed the disks that weren't in use at all. But those were only 4 1GB ones. However, there are 3 100GB ones in use, and I have no idea what app/deployment using them (except that it's Kubernetes). Also, there are 4 10GB disks in use by something called `tk-vagrant-main-ubuntu-1404-23cee4`, which I have no idea what it could be (that one's not Kubernetes). @gregkare Any idea what's going on there?

greg commented

2019-03-04 20:01:30 +00:00

The tk disks are from running the integrations tests on the chef repo using GKE

greg commented

2019-03-04 20:08:10 +00:00

I don't know what the 100GB disks are, they're not any of the persistent disks in the GKE console

raucao commented

2019-03-05 02:32:08 +00:00

The tk disks are from running the integrations tests on the chef repo using GKE

Interesting. Why/how are they creating GCE disks?

> The tk disks are from running the integrations tests on the chef repo using GKE Interesting. Why/how are they creating GCE disks?

greg commented

2019-03-06 08:58:48 +00:00

I need to figure out why it's creating persistent disks. The integrations tests are using Test Kitchen with the gce driver, because the Vagrant driver didn't work inside of Kubernetes

I need to figure out why it's creating persistent disks. The integrations tests are using [Test Kitchen](https://kitchen.ci/) with the gce driver, because the Vagrant driver didn't work inside of Kubernetes

greg commented

2019-03-29 14:13:10 +00:00

I checked again, there aren't any tk-vagrant-main-ubuntu persistent disks right now

raucao closed this issue

2020-07-30 10:59:20 +00:00

This repo is archived. You cannot comment on issues.