Repository navigation
[BUG] gitlab (selfhosted) PATs not working #412
Description
Describe the bug
gitlab (selfhosted) PATs not working
To Reproduce
Create a fully scoped PAT in a local gitlab instance.
Setup a VC in Kubernetes, having the following:
selfhosted:
- name: gitlab
host: XXX
token: "glpat-YYY"
ca_path: "ZZZ"
Install VC helm.
Check VC pod logs and see:
time="2025-12-24T13:06:22Z" level=error msg="failed to sync pod XXX: failed to check container image \"XXX\": failed to get tags from remote registry for \"XXX\": {\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"authentication required\",\"detail\":[{\"Type\":\"repository\",\"Class\":\"\",\"Name\":\"XXX\",\"ProjectPath\":\"\",\"Action\":\"pull\"}]}]}\nFailed to process pod" component=controller controller=pod pod=XXX
Moreover, the gitlab UI would be showing the PAT as not used.
Seems to me the VC selfhosted client is not using the token at all.
Expected behavior
Selfhosted should support gitlab.
Environment (please complete the following information):
- Version-Checker: 0.1.0
- Kubernetes: v1.34.1
- Gitlab: 17.6
Reacted by Copilot
Activity
[-][BUG][/-][+][BUG] gitlab (selfhosted) PATs not working[/+]github-actions commentedon Mar 25, 2026
This issue has been automatically marked as stale because it has not had
any activity in the last 90 days. It will be closed if no further activity
occurs. Thank you for your contributions.