Configuring DC/OS access for Spinnaker


How to use Spinakker with DC/OS

This section is a quick guide on how to configure and use Spinnaker with DC/OS.


  • A running DC/OS 1.10 or 1.11 cluster


DC/OS Spinnaker is an automated service that makes it easy to deploy and manage Spinnaker on DC/OS.

Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers. The Spinnaker service is a micro service composition. You can read a good overview on the micro services involved here.

IMPORTANT: The DC/OS Spinnaker service currently only works with DC/OS Enterprise.

Installing with Defaults

This section provides a quick and easy procedure for configuring and installing Spinnaker. You can find different custom configurations in the Configuration section of these documents.

From the CLI

The DC/OS Spinnaker service uses minio, an s3-compatible backing store for the Spinnaker front50 service.

  1. To get started run the following two commands:
dcos package install marathon-lb --yes
dcos package install minio --yes
  1. marathon-lb will make the minio web interface accessible via the DC/OS public agent. In your browser enter the following address.

The minio credentials are minio / minio123.

The DC/OS Spinnaker service allows you to deliver to the DC/OS cluster the service runs itself in. The Spinnaker deck and gate services will be made available via a proxy or Edge-LB running on the DC/OS cluster’s public agent. Note down the hostname/ip of the public agent <public-agent-ip> in your DC/OS cluster.

From the web interface

  1. In the DC/OS catalog/universe, select Spinnaker, which will show you the following package description.

Spinnaker Quick Start

Figure 1. Spinnaker package

  1. Select Review & Run.

  2. In the service section fill in the proxy hostname with the hostname of the public agent noted down earlier.

Spinnaker Quick Start

Figure 2. Service section

  1. If minio and DC/OS default credentials are available, then you are ready to select Review & Run. Otherwise the next two steps show how to configure your specific credentials.

Spinnaker Quick Start

Figure 3. Default credentials available

  1. Configure the minio credentials as shown on the following screen.

Spinnaker Quick Start

Figure 4. Minio credentials

  1. Configure the DC/OS credentials as shown on the following screen.

Spinnaker Quick Start

Figure 5. DC/OS credentials

  1. Once the service is running, launch a simple proxy to get access to the Spinnaker deck and gate service. Create the marathon proxy.json file with the following content and add the marathon app.
  "id": "spinnaker-proxy",
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "mesosphere/spinproxy2",
      "forcePullImage": true
  "args": [],
  "cpus": 0.1,
  "mem": 256,
  "env": {
  "instances": 1,
  "constraints": [],
  "acceptedResourceRoles": [
dcos marathon app add proxy.json
  1. Go to the Using Spinnaker section to learn how to access the Spinnaker web interface, and to get an overview of the Spinnaker concepts with samples.

Using Spinnaker

Go to your browser and enter the following url to get to the Spinnaker user interface.