Renovate Self Hosted uses external dns to connect to repo #33983
Unanswered
adamcirillo
asked this question in
Request Help
Replies: 1 comment 2 replies
-
this is because Forgejo returned those urls in next page header this needs to be implemented for Forgejo you should find more discussions about this |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Kubernetes 1.32.1 with Forgejo 10.0.0 Renovate 39.153.0
Please tell us more about your question or problem
I've installed renovate on my kubernetes cluster with the helm chart when it scans the repo i've setup with the json instead of connecting to http://forgejo-http.forgejo.svc.adamhf.cluster.local:3000 it connects to https://git.domain.name which is the external dns i have configed on envoy gateway's http route this works for traffic outside the cluster but internal does not work through this so i was trying to force renovate to connect to the internal point since its running on the same cluster. i've also tried this in the renovate config and the renovate json in the repo as did not work.
helm values
renovate json in repo
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions