Chopping down the Let's Encrypt Testflume CT Log

[Phil Porada]

Hi everybody,

We're going to be completely shutting down the Testflume testing log tomorrow, May 4th, 2022. Testflume has been unable to accept new submissions for several months due to running out of space[1]. We will be destroying the Testflume 2019, 2020, 2021, 2022, and 2023 shards, related infrastructure, and data. Testflume's intended purpose has always been to test new versions of Trillian, certificate-transparency-go, and Kubernetes before deploying them to our Oak production log. History of the path that lead to this decision can be found here[1] and here[2]. We will be spinning up a brand new public testing log in the coming days and will announce it in a separate post.

If you are still reliant upon Testflume for testing submissions, please view ct-test-srv[3] code which implements RFC 6962 add-chain and add-pre-chain endpoints.

[1] https://groups.google.com/a/chromium.org/g/ct-policy/c/madcUcQZ1IQ

[2] https://groups.google.com/a/chromium.org/g/ct-policy/c/9fTOoC4UzmE

[3] https://github.com/letsencrypt/boulder/tree/main/test/ct-test-srv

[Phil Porada]

Testflume has been destroyed.