0

On my multi-node RKE2 cluster I have been trying to deploy a gitrepo fleet resource, but when the system tries to get the repository, it tries going through the https proxy, which blocks communication to that repository. The events page is shown below

Events:
  Type     Reason               Age   From          Message
  ----     ------               ----  ----          -------
  Warning  FailedToCheckCommit  6s    fleet-gitops  Get "https://bitbucket.***.com/**/**/**.git/info/refs?service=git-upload-pack": read tcp 10.42.3.24:55690-><HTTPS_Proxy IP>:80: read: connection reset by peer

My fleet deployment is:

apiVersion: fleet.cattle.io/v1alpha1
kind: GitRepo
metadata:
  name: rancher-tools
  namespace: fleet-local
spec:
  repo: "https://bitbucket.***.com/**/**/**.git"
  branch: "feature/***"
  clientSecretName: gitcredential
  paths:
  - helm/rancherui

My gitcrendential secret is:

apiVersion: v1
kind: Secret
metadata:
  name: gitcredential
  namespace: fleet-local
type: Opaque
data:
  username: ***
  password: ***

I've tried updating the no_proxy of all the systems, both the environment variable and the RKE2 and the setting in /etc/default/rke2-server/rke2-server. I also have tried using a ssh URL instead of the http URL and it gets to starting to build the job, but then fails on cloning the repo saying invalid auth method. I have tried the ssh credentials on a blank vm and they work fine there. I have also tried a basic-auth secret instead of an Opaque secret, but that did not work either.

Mudrock
  • 1

1 Answers1

0

In my researching into this problem, I replaced the domain name of the repo with its IP and I revived a 503 service unavailable errors. This implies to me that bitbucket does not support the routes the fleet needs to function. When I moved the repo onto GitLab, it worked without any problems.

Mudrock
  • 1