search

GoogleCloudPlatform / spinnaker-for-gcp

Production-ready Spinnaker on GKE
175 stars 131 forks source link

The connection to the server localhost:8080 was refused #225

Open rajbainsTestAccount opened 3 years ago

rajbainsTestAccount commented 3 years ago

I am not sure if this was a shortcoming of instructions or I missed reading something, so reporting this just in case someone else see this issue.

I kept getting the below error which seems like a coding issue on line 295 or a firewall issue with local host port 8080. I pre-created the GKE cluster and it all worked fine.

Line 295 in spinnaker-for-gcp/scripts/install/setup.sh: if [ $EXISTING_HAL_DEPLOY_APPLY_JOB_NAME != 'null' ]; then


/home/bains/cloudshell_open/spinnaker-for-gcp/scripts/install/setup.sh: line 295: [: !=: unary operator expected
.  Provisioning Spinnaker resources... 
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting on job hal-deploy-apply to completeThe connection to the server localhost:8080 was refused - did you specify the right host or port?```
csaroka commented 3 years ago

The K8s version is hardcoded under the variable name GKE_CLUSTER_VERSION and it is outdated (1.15.12); no longer available. Search for instances of it in the install directory (setup_properties.sh) and try updating the value to a current release. See https://cloud.google.com/kubernetes-engine/docs/release-notes for options. After updating the value to 1.18.16, the Spinnaker cluster deployed successfully in a test environment.

mattuLA commented 3 years ago

This is still an issue even with the GKE version currently set to 1.18.20. Leaving all options as defaults results in the above error each time. Installer is non-functional until this is resolved.

mattuLA commented 3 years ago

Update: Changing the cluster version to 1.20.10 resolves this issue.

I see we have a couple pull requests pending to both update the cluster version in the installer or to just use the current stable version instead. Is there any ETA on these fixes being completed?