After installing Spinnaker and navigating to the Applications screen, you may see one of following issues:
Error fetching applications. Check that your gate endpoint is accessible. Further information on troubleshooting this error is available here
The most common cause of this error is that your browser can’t communicate with your Gate endpoint.
(This endpoint defaults to
http://localhost:8084, but can be customized.)
Check your browser console log and/or network for any failed requests to
Some things to check while troubleshooting:
http://localhost:9000, check that you have forwarded Gate’s port (8084 by default) to the machine where your browser is running.
override-base-urlfor both the UI (Deck) and API (Gate) services, as described in the question below . These settings will configure cross-origin resource sharing (CORS) between your Gate and Deck endpoints; if this is not properly configured, your browser will reject requests from Deck to Gate.
sudo systemctl enable redis-server && sudo systemctl start redis-serverand restart spinnaker by running
sudo systemctl restart spinnaker.
First off, on a local deployment Spinnaker binds to
Your Spinnaker instance has the ability to deploy and destroy a lot of
infrastructure in whatever accounts it manages, and opening it to the public is
not a good idea without authentication enabled. With that in mind, there are
Once you enable an
will bind the UI and API servers to
0.0.0.0 automatically. This is
if you prefer to bind a specify
address instead. Regardless, you still need to set the API &
UI baseUrls so CORS and login redirects happen correctly, this is done with
hal config security ui edit --override-base-url <full ui url>
hal config security api edit --override-base-url <full api url>.
If you don’t want to rely on authentication, you can follow this guide . This makes sense if you’re running Spinnaker in a private network, or have another form of authentication fronting Spinnaker.
Odds are Halyard can’t connect to the configuration & version bucket (in Google
Cloud Storage) it uses to determine if the configuration you’ve provided works
for the version of Spinnaker you want to install. The bucket is
gs://halconfig, see if you can reach it locally using the
The remediation will depend on your local network. You can also always omit
validation with the
As an alternative to
gsutil, you can try querying the bucket directly using its
If this happens, there are one of two causes:
hal deploy collect-logsto collect service logs, which will be placed in
~/.hal/default/service-logs. Check for any obvious errors.
First, please read the
documentation. With that in mind, if you’re configuring any of Spinnaker’s
services (everything but deck), you’re
best off providing a
-local.yml profile for the service in mind. For example,
say you are configuring the Halyard
default, and the service
gate, you can write the following file:
example: property: value
and the properties generated by Halyard will be overwritten by those provided
If the service you want to configure does not rely on Spring, you will need to
wholesale overwrite the config in the
You have two options here:
--omit-configflag. In the Local installation, this will pin & download validated debian packages at their respective versions without providing any configuration. In a Distributed installation, you will need to provide your own mechanisms for loading configuration for each subservice.
Spinnaker’s cloud provider integration point (clouddriver) does not clean out
cache entries that may be left around after reconfiguring existing
accounts. The best way to get around this is to supply the
--flush-infrastructure-caches to a
hal deploy apply. This may cause
jittering in the UI as the caches are repopulated.
Please read the backup documentation .
You can supply the flags
-q -log=info to any Halyard command to get more
digestable log messages.
-q suppresses the ANSI pretty-printing, and
-log=info enables info-level logs in the CLI.
Anything in the
~/.hal/config can be edited by hand at any time. You can
validate what you provide there by running
hal config, and deploy it as you
hal deploy apply. For more service-specific edits, please read
You can run
hal deploy apply --service-names <service1> <service2...> to
deploy only the services you care about. Be careful, if you have sidecars like
monitoring-daemon or the
consul-client for a VM based distributed
deployment, you will have to supply those as well.
This can be coupled with
--omit-config in a local installation to provide a
taylored way of deploying & configuring only the services you want on the
machines you care about.
In the file under
/opt/halyard/bin/halyard, add the necessary proxy
configuration to the variable
DEFAULT_JVM_OPTS as described
For most Spinnaker service communication, this can be accomplished by setting appropriate
JVM options for the service you want to proxy. For example, if you wanted to proxy Echo
communication for Slack notifications, you would add the following proxy settings to
env: JAVA_OPTS: "-XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -XX:MaxRAMFraction=2 -Dhttp.proxyHost=<proxy host> -Dhttp.proxyPort=<proxy port> -Dhttps.proxyHost=<proxy host> -Dhttps.proxyPort=<proxy port> -Dhttp.nonProxyHosts='localhost|127.*|[::1]|*.spinnaker'"
These settings will forward all external communication through the proxy server specified while keeping internal traffic non-proxied. Additional information can be found here.
The Kubernetes provider must be handled differently. Because the Kubernetes provider
kubectl (which uses curl), you must set environment variables if you want
Kubernetes traffic to be proxied.
clouddriver.yml that will proxy Kubernetes traffic will look like:
env: HTTP_PROXY: 'proxyaddress:proxyport' HTTPS_PROXY: 'proxyaddress:proxyport' NO_PROXY: 'localhost,127.0.0.1,*.spinnaker'
hal deploy clean to delete an existing Spinnaker deployment. Note that this command destroys all Spinnaker artifacts in your target deployment environment. So, use it with caution and back up your configuration in case you want to restore it.
After Spinnaker is deleted, delete Halyard by running