From ca64fac64021b7470ea96712921b65502a4d4556 Mon Sep 17 00:00:00 2001 From: Paulo Gomes Date: Tue, 22 Mar 2022 19:22:19 +0000 Subject: [PATCH] Add experimental transport to spec documentation. Signed-off-by: Paulo Gomes --- docs/spec/v1beta2/gitrepositories.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/spec/v1beta2/gitrepositories.md b/docs/spec/v1beta2/gitrepositories.md index fd30b6cfd..720be7fe0 100644 --- a/docs/spec/v1beta2/gitrepositories.md +++ b/docs/spec/v1beta2/gitrepositories.md @@ -384,6 +384,17 @@ Some Git providers like Azure DevOps _require_ the `libgit2` implementation, as their Git servers provide only support for the [v2 protocol](https://git-scm.com/docs/protocol-v2). +#### Experimental managed transport for `libgit2` Git implementation + +The `libgit2` Git implementation supports a new experimental transport for +improved reliability, adding timeout enforcement for Git network operations. +Opt-in by setting the environment variable `EXPERIMENTAL_GIT_TRANSPORT` to +`true` in the controller's Deployment. This will result in the low-level +transport being handled by the controller, instead of `libgit2`. + +This may lead to an increased number of timeout messages in the logs, however +it will fix the bug in which Git operations make the controllers hang indefinitely. + #### Proxy support When a proxy is configured in the source-controller Pod through the appropriate