Yes, for me it was that the pod wasn't defined properly in the cloud
configuration within Jenkins and all seems to be right. I just need to
expose the jnlp ports outside the cluster so the jnlp container can
communicate with Jenkins in the other cluster. Thanks for your help,
appreciate it
Steve
kubectl describe pod
would tell why the pod can't start.
If you are using private registry, "pull image secret" is required.
Sometimes a manual "docker logout" on the worker node help with image pull.
On Thu, Mar 7, 2019 at 12:05 PM Steve Garrett
wrote:
> Hi, was able to figure that out, thanks
Hi, was able to figure that out, thanks for your help there. Now I get a
different problem. My pod gets created now on the right cluster but it
seems to fail to pull the image. When I go onto any of the worker nodes
I'm able to do a docker pull and it works just fine. What am I doing wrong?
Th
Hi,
in the podTemplate, I'm using scripted jenkinsfiles so does that still
apply? I've never seen a cloud parameter before.
Thanks,
Steve
On Thursday, March 7, 2019 at 4:42:24 AM UTC-5, Carlos Sanchez wrote:
>
> are you creating pod templates in UI or in pipeline?
>
> in UI is just a matter
are you creating pod templates in UI or in pipeline?
in UI is just a matter of assigning different labels to different pod
templates in different clouds
in pipeline you can pass an argument "cloud" to podTemplate
On Wed, Mar 6, 2019 at 8:23 PM Steve Garrett
wrote:
> Hi,
>
> I'm trying to use mu
