Hi, i'm a gocd newbie and having an issue getting the hello world gocd in 
kubernetes to work.

Followed tutorial in https://docs.gocd.org/current/gocd_on_kubernetes/. I'm 
running on Docker Desktop. 

The issue when i start a build using elastic agent, the new agent can't 
connect to the server.
Because the gocd server url is http://gocd-server:8153/go but it needs to 
be https. 
 
Log snippet:
[Mon May 03 21:47:02 GMT 2021] Starting process:
[Mon May 03 21:47:02 GMT 2021] Working directory : /go
[Mon May 03 21:47:02 GMT 2021] Application arguments: [-serverUrl, 
http://gocd-server:8153/go]
[Mon May 03 21:47:02 GMT 2021] GoCD Version: 18.3.0-6540

...
-serverUrl must be an HTTPS url and must begin with https://
Usage: java -jar agent-bootstrapper.jar [options]
Options:
-help
Print this help
-rootCertFile
The root certificate from the certificate chain of the GoCD server (in
PEM format)

-serverUrl
The GoCD server URL. Must begin with https://, and end with /go
-sslVerificationMode

Tracing it back to the helm chart, that is coming 
from 
https://github.com/gocd/helm-chart/blob/master/gocd/templates/gocd-agent-deployment.yaml#L78

The tutorial seems to suggest simple helm install the chart and everything 
should work. 
But it doesn't look that's the case.

I'm curios how folks for the helm chart working. and what setup (minikube, 
docker desktop, KinD, GKE, etc) they used. Did you have to do anything 
extra to get the cluster working? 

A user created an issue on the 
SSL https://github.com/gocd/helm-chart/issues/12 but there's been no action 
on it. 

I've tried with minikube but the build fails because minikube can't handle 
external DNS resolution. In this case fails when it tries to resolve 
github.com 



 

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/ad97ff95-8845-4dca-bc4b-ed0bb416348en%40googlegroups.com.

Reply via email to