Skip to content

Investigate behavior of GCS driver with HTTP/2

Context

Related to https://gitlab.com/gitlab-com/core-sub-department/section-core-request-for-help/-/issues/125, where a customer reported failed pushes to their registry, which was using GCS. At the end, it turned out that the registry was relying on HTTP/2 when talking with GCS and this end up causing problems. Disabling HTTP/2 via GODEBUG=http2client=0 solved the problem.

Task

  • Try to reproduce the issue by getting the registry to talk with a GCS bucket over HTTP/2
  • Find potential issue leading to request failures/retries
  • Determine why we're not seeing this problem on .com and it was not reported by any other self-managed customer so far