Sameer Vohra

Experienced this again week of Dec 16 - Dec 20th ( primarily on Dec 17th and 20th ) Here are some screenshots with what we observed * Dec 17th *...

It does appear that based on our GC logic that volumes in the DB but not on the worker should be cleaned up eventually ( worker GC tick to report...

Seeing this again on Hush House today. 3 workers experiencing what appear to be the same issue where they are not able to clean up volumes due to ``` "pq:...

@marco-m we believe that issue is more related to not having enough docs to specify one of `regexp` or `versioned_file` is required whereas this one is more about "s3-compatible" object...

One possible workaround is that instead of using the `versioned_file` configuration, using `regexp` instead will by pass checking that header. https://github.com/concourse/s3-resource/blob/84741092da864119fa7bc64654804c880de4c34c/out/command.go#L81-L89

TODO - Document the permissions required to setup the baggageclaim CSI + Storage Class

Hey @ddadlani @vito Does it make sense to close this issue now, since we're going to be spiking on fetching base resources using a registry #3923 & the [RFC](https://github.com/vito/rfcs/blob/extract-core-resources/030-extract-core-resources/proposal.md) ?

Nader and I were discussing this. Some other ideas we could also explore/consider; - embed bootstrapping functionality into Concourse to be able to fetch the registry image resource, which is...

Another wild wild idea to consider would be to use Garden's ability to fetch an image 1. Concourse schedules a container which uses `registry-image-resource` as an image ref, relying on...