We have a gitlab deployment in our local kubernetes cluster and it works perfect.
I’m trying to install jenkins x and/or gitalb-ci. These two aplication that interact with the api, both repond to me and the same way and i do not understand why.
The integration with our cluster works fine because I can see the pod of the runner, but unable to interact with it. The ip that is showing is the node where the pod for ingress default backend is.
WARNING: Checking for jobs... failed runner=584ZxT3m status=couldn't execute POST against https://gitlab.****.com/api/v4/jobs/request: Post https://gitlab.gyf.com/api/v4/jobs/request: dial tcp 192.168.0.62:443: getsockopt: no route to host
The ip that is showing is the one of my ingress load balancer.
I’m just running the
jx boot command and input the requested requirements and after the
STEP: verify-jenkins-x-environment it fails with the next error:
DEBUG: getting repository root/environment-kubernetes-dev: failed to get repository root/environment-kubernetes-dev due to: Get https://gitlab.***.com/api/v3/repos/root/environment-kubernetes-dev: dial tcp 192.168.20.250:443: connect: no route to host error: creating remote for dev environment environment-kubernetes-dev: duplicating https://github.com/jenkins-x/jenkins-x-boot-config to root/environment-kubernetes-dev: getting repo for https://github.com/jenkins-x/jenkins-x-boot-config: failed to get repository jenkins-x/jenkins-x-boot-config due to: Get https://gitlab.***.com/api/v3/repos/jenkins-x/jenkins-x-boot-config: dial tcp 192.168.20.250:443: connect: no route to host error: failed to interpret pipeline file jenkins-x.yml: failed to run '/bin/sh -c jx step verify env' command in directory '.', output: ''
Thank you for your time.