search

jenkins-x / jx

Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Cloud Native pipelines from Tekton
https://jenkins-x.io/
Apache License 2.0
4.58k stars 788 forks source link

Unable to set the default docker-registry for PKS during installation #5073

Closed laikw closed 5 years ago

laikw commented 5 years ago

Summary

Installing Jenkins X to a PKS cluster with --docker-registry does not change the default docker registry: jx install --docker-registry harbor.pks.abc.com

Steps to reproduce the behavior

Installed Jenkins X a PKS 1.4.1 cluster with a custom docker registry. Created a golang-http quickstart application and the step "Build Container Build" failed.

jx get build logs returns: error pushing image: failed to push to destination harbor.corp.local/***/-go:0.0.2: Get http://harbor.corp.local/v2/: dial tcp: lookup harbor.corp.local on 10.100.200.2:53: no such host

Expected behavior

The image should be pushed to the docker registry "harbor.pks.abc.com" which is specified during installation.

Actual behavior

The image got pushed to the default docker registry for PKS, "harbor.corp.local".

Jx version

The output of jx version is:

NAME               VERSION
jx                 2.0.589
jenkins x platform 2.0.942
Kubernetes cluster v1.13.5
kubectl            v1.15.2
helm client        Client: v2.14.3+g0e7f3b6
git                2.7.4
Operating System   Ubuntu 16.04.6 LTS

Jenkins type

Note that in Classic Jenkins, the --docker-registry is able to set the default docker registry.

Kubernetes cluster

Created using PKS 1.4.1. The kubernetes cluster version is v1.13.5.

Operating system / Environment

Ubuntu 16.04.6 LTS

pmuir commented 5 years ago

This may be a bug in serverless install or in PKS. Do you know?

laikw commented 5 years ago

I do not know but my guess would be this is a bug in serverless JX since it is the one pushing the image to the docker registry.

On 15 Aug 2019, at 6:16 AM, Pete Muir notifications@github.com wrote:

This may be a bug in serverless install or in PKS. Do you know?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jenkins-x/jx/issues/5073?email_source=notifications&email_token=AL7HBYYR2UANIUSG3CCNIEDQER72VA5CNFSM4ILKIK32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4KIYTQ#issuecomment-521440334, or mute the thread https://github.com/notifications/unsubscribe-auth/AL7HBY6NYHWZDWUG2OOXNODQER72VANCNFSM4ILKIK3Q.

laikw commented 5 years ago

Seems like this issue is caused by PKS rather than JX. Closing this issue.