Hello, GoCD made changes to the agent server communication in version 20.2.0. On GoCD v18.3.0, agents connect to the gocd server on https://gocd-server:8154/go. There are two ways you can work around this: 1. Use an old helm chart version to match the application version v18.3.0. You can find the chart versions corresponding application versions on https://helm.sh. This would mean that you won't get the helm chart bug fixes etc that have been made since the old helm chart version 2. Specify the GO_SERVER_URL environment variable as https://gocd-server:8154/go in values.yaml while installing the helm chart. It's under agent.env in values.yaml
Cheers On Tuesday, 4 May 2021 at 08:11:46 UTC-7 [email protected] wrote: > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/1fc7c4b1-f28b-4f89-ba63-50aa5f5cb11bn%40googlegroups.com.
