Root cause DIND not working in Shared Runners after update
We are trying to update the shared linux runners to 16.8
to rollout native GCP Secrets Manager support. However the initial rollout caused an incident so it was rolled back. The incident was due to docker-in-docker (dind) failures, not related to secrets manager. However we still haven't identified a root cause, so we cannot retry the rollout.
This issue tracks the work to identify the root cause of the dind failures.