Trask Stalnaker

> we will need to open a CNCF Legal ticket @jpkrohling can you take this on as the operator SIG's GC liaison?

Copilot failed at this task. In any case, I do tend to agree that the term percentage generally means a number between 0-100. "Ratio" is another option.

You can see cache usage here, e.g. - https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/caches - https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/caches These two repos for example show the problem I think GitHub is addressing, which is that they don't seem...

I found this overview in the org settings: | Repository | Cache Usage | Active Caches | |------------|-------------|---------------| | opentelemetry-java-instrumentation | 485 GB | 1243 | | opentelemetry-go-instrumentation | 110...

^^ cc @open-telemetry/java-instrumentation-maintainers @open-telemetry/go-instrumentation-maintainers @open-telemetry/collector-contrib-maintainers @open-telemetry/weaver-maintainers @open-telemetry/java-maintainers @open-telemetry/ruby-maintainers @open-telemetry/go-maintainers @open-telemetry/php-maintainers @open-telemetry/demo-maintainers

> Just to make sure I'm understanding this correctly, we don't need to take any action, but should keep an eye on our CI speed to see if we'd like...

just fyi, enforcement date has been moved back from mid-October to November: https://github.blog/changelog/2025-09-29-new-date-for-enforcement-of-cache-eviction-policy/

hi @pellared, I'll open a CNCF ticket to ask about this, what would you like the limit to be for each one?

> **After this date**, all repositories will receive 10GB for free and have the option to pay for additional storage at a per GB/month rate that is checked at hourly...

Looks like it's happening now: https://github.blog/changelog/2025-11-20-github-actions-cache-size-can-now-exceed-10-gb-per-repository/ Found this new setting: