Cloud Providers Overview on Spinnaker

Azure

Mon, 01 Jan 0001 00:00:00 +0000

In Azure , an Account maps to a credential able to authenticate against a given Azure subscription .

Prerequisites

You need a Service Principal to authenticate with Azure and a Key Vault to store a default username/ssh public key for deployed VM Scale Sets . The next steps assume the use of the Azure CLI 2.0 . The example commands will set environment variables along the way for use when creating an account in the final stage. You can check that you have az installed by running:

Cloud Foundry

Mon, 01 Jan 0001 00:00:00 +0000

In Cloud Foundry (CF), an Account maps to a user account on a CF foundation (a BOSH Director and all the VMs it deploys). You can add multiple accounts for one or more CF foundations.

Prerequisites

Your CF foundations’ API endpoints must be reachable from your installation of Spinnaker.

Add an account

First, make sure that the provider is enabled and add an account named my-cf-account to the clouddriver list of Cloud Foundry accounts: in ~/spinnaker-kustomize/overlays/config/files/clouddriver-local.yml

Docker Registry

Mon, 01 Jan 0001 00:00:00 +0000

:warning: This only acts as a source of images, and does not include support for deploying Docker images.

When configuring Docker Registries, an Account maps to a credential able to authenticate against a certain set of Docker repositories .

Prerequisites

The Docker Registry you are configuring must already exist.
That Registry must support the v2 registry API . OCI registries are ALSO supported at this time.

Registry providers

You can set up a Docker Registry provider for Spinnaker using any of the repositories listed here. Each one supports the same API, but there are subtle differences in how to get them to work with Spinnaker.

Google App Engine

Mon, 01 Jan 0001 00:00:00 +0000

In Google App Engine , an Account maps to a credential able to authenticate against a given Google Cloud Platform project.

Prerequisites

You need a Google Cloud Platform project to run Spinnaker against. The next steps assume you’ve already created a project , and installed gcloud . You can check that gcloud is installed and authenticated by running:

gcloud info

If this is your first time deploying to App Engine in your project, create an App Engine application. You cannot change your application’s region, so pick wisely:

Google Cloud Run

Mon, 01 Jan 0001 00:00:00 +0000

In Google Cloud Run , an Account maps to a credential able to authenticate against a given Google Cloud Platform project.

Prerequisites

gcloud info

To initialize the gcloud CLI, run the following command:

gcloud init

If this is your first time deploying to Cloud Run in your project, create a Cloud Run application.

Google Compute Engine

Mon, 01 Jan 0001 00:00:00 +0000

In Google Compute Engine (GCE), an Account maps to a credential able to authenticate against a given Google Cloud Platform (GCP) project.

Prerequisites

You need a Google Cloud Platform (GCP) project to run Spinnaker against. The next steps assume you’ve already created a project , and installed gcloud . You can check that gcloud is installed and authenticated by running:

gcloud info

Downloading credentials

Spinnaker needs a service account to authenticate as against GCE, with the role enumerated below enabled. If you don’t already have such a service account with the corresponding JSON key downloaded, you can run the following commands to do so:

Oracle

Mon, 01 Jan 0001 00:00:00 +0000

In Oracle Cloud , a Spinnaker Account maps to an Oracle Cloud Infrastructure user .

Prerequisites

You will need the following to enable Oracle Cloud provider in Spinnaker:

A user in IAM for the person or system who will be using Spinnaker, and put that user in at least one IAM group with any desired permissions. See Adding Users .
The user’s home region. See Managing Regions . (e.g. --region us-ashburn-1)
RSA key pair in PEM format (minimum 2048 bits). See How to Generate an API Signing Key . (e.g. --ssh-private-key-file-path /home/ubuntu/.oci/myPrivateKey.pem)
Fingerprint of the public key. See How to Get the Fingerprint of the Key . (e.g. --fingerprint 11:22:33:..:aa)
Tenancy’s OCID and user’s OCID. See Where to Get the Tenancy and User OCIDs . (e.g. --tenancyId ocid1.tenancy.oc1..aa... --user-id ocid1.user.oc1..aa...)
Compartment OCID: On Oracle Cloud Console, open the navigation menu. Under Governance and Administration, go to Identity and click Compartments. See Managing Compartments . (e.g. --compartment-id ocid1.compartment.oc1..aa...)
Upload the public key from the key pair in the Console. See How to Upload the Public Key .

Add an Oracle Cloud account

Enable the Oracle Cloud provider and add the account

oracle:
  enabled: true
  accounts:
  - name: my-oci-acct
    compartment-id: ocid1.compartment.oc1..aaaaaaaatjuwhxwkspkxhumqke4o73b2b
    fingerprint: 8f:05:f4:94:f3:5f:e3:30:ec:35 
    region: us-phoenix-1
    ssh-private-key-file-path: /mnt/secrets/oci_api_key.pem
    tenancyId: ocid1.tenancy.oc1..aaaaaaaa225wmphohi3iiyxxxjruo
    userId: ocid1.user.oc1..aaaaaaaagosdr3zsh67tvgpnmw42ywqc

Next steps

Optionally, you can set up another cloud provider or continue the installation instructions