Deploy Spinnaker and Connect to the UI

Now that we’ve enabled one or more Cloud Providers , picked a Deployment Environment , and configured Persistent Storage , we’re ready to pick a version of Spinnaker, deploy it, and connect to it.

Pick a version

1. See the available versions on the versions page

   You can follow the links to the versions’ respective changelogs to see what features each adds.

2. Set the version you want to use: Set this on the kustomize image tag configuration . All spinnaker versions since the monorepo use the same image tags, e.g. 2025.3.2.

Deploy Spinnaker

kubectl kustomize -o ./spinnaker.yaml
kubectl apply -f ./spinnaker.yaml

Ingress

A default ingress is included that uses a single ingress with path based routes to gate’s API on a prefix. This bypasses CORS issues and enables a simple user experience to connect to spinnaker. The default username and passwords are also set in this installation. For ingress specific to your environment, please adjust the default ingress as needed for your use case.

Connect to the Spinnaker UI

Once deployed, get the address for your ingress controller and connect to the ingress. Make sure you have a domain address pointing to your new endpoint. Example:

k get ingress -n spinnaker
NAME                CLASS   HOSTS                     ADDRESS          PORTS     AGE
spinnaker-ingress   nginx   spinnaker.example.com     192.168.1.2      80, 443   644d

This ingress would include 443 or TLS as configured. It’s recommended to enable a cert provider and use HTTPS for requests but this is out of the scope of the installation.
See the kubernetes networking documentation on TLS for information on modifying the ingress for certificate handling.

Once you’ve configured DNS to point to your address, go to http://spinnaker.example.com/ and login with the username and password that you’ve configured (or your SSO provider if so configured per authentication configuration

Troubleshooting

First, check that services are running. IF a service isn’t running, check the logs for configuration errors.

Next once all services are running, make sure you can talk to the gate endpoint. You should be able to check the health endpoint even externally via the gate-api/health endpoint.

Upgrade Spinnaker

To upgrade, read the release notes and change the images to the newer versions. Adjust any config that’s been removed/changed as needed.

Next steps

Now that Spinnaker is deployed and capable managing your cloud provider, you can…

• Continue with additional configuration, such as your image bakery

• If you’re a Spinnaker end user, read how to get started using Spinnaker

• Visit the Guides pages to learn more

Remember to keep your configuration in git for both history and changes!