Providers on Spinnaker

Amazon ECS

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

Resource mapping

Server group

A Spinnaker server group maps to an Amazon ECS service .

There are two ways to specify server group settings for Amazon ECS:

Inputs (default): Specify the container image, resource limits, and other settings needed to create an Amazon ECS task definition and service directly in the server group. This option supports deploying one container per Amazon ECS task (equivalent to a Spinnaker “instance”).
Artifact (supported as of 1.15.0): Specify a pipeline artifact to use as an Amazon ECS task definition for the service. The artifact should be a JSON file in the format of an Amazon ECS Register Task Definiton request . This option also requires that you specify containerName:imageDescription mappings for each image in your pipeline that you want to be deployed within the service. You can deploy multiple containers (up to 10) per Amazon ECS task using this option.

Amazon Web Services

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

Reference documentation coming soon!

See setup here

Azure

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

If you are not familiar with Azure or any of the terms used below, please consult the Azure reference documentation .

Resource mapping

Account

In Azure (AZ), an Account maps to a credential able to authenticate against a given Azure (AZ) project - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an Azure Application Gateway .

Server Group

A Spinnaker server group maps to an Azure Virtual Machine Scale Set .

Instance

A Spinnaker instance maps to an Azure Virtual Machine Instance .

Cloud Foundry

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

If you are not familiar with Cloud Foundry (CF) or any of the terms used below, please consult Cloud Foundry’s reference documentation .

Resource mapping

Account

In CF, an Account maps to a user account on a CF foundation (where a foundation is a BOSH Director and all the VMs it deploys). This user account is provided via configuration to Spinnaker, and Spinnaker’s privileges are determined by the CF user account’s permissions; for example, Spinnaker can manage CF apps across all of the orgs and spaces which its CF user account can access.

Google App Engine

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

If you are not familiar with App Engine or any of the terms used below, please consult App Engine’s reference documentation .

Resource mapping

Account

A Spinnaker account maps to a single App Engine application, a top-level resource that contains services, versions, and instances. Spinnaker authenticates itself with App Engine using service account credentials for a Google Cloud Platform project - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an App Engine service.

Google Cloud Run

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

If you are not familiar with Cloud Run or any of the terms used below, please consult Cloud Run’s reference documentation .

Resource mapping

Account

A Spinnaker account maps to a single Cloud Run application, a top-level resource that contains services, versions, and instances. Spinnaker authenticates itself with Cloud Run using service account credentials for a Google Cloud Platform project - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an Cloud Run service.

Google Compute Engine

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

If you are not familiar with Google Compute Engine or any of the terms used below, please consult Compute Engine’s reference documentation .

Resource mapping

Account

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

Load Balancer

A Spinnaker load balancer maps to a GCE load balancer .

GCE supports many different types of load balancers, including: HTTPS(S), SSL Proxy, Network and Internal. Each of these is supported by Spinnaker.

Kubernetes Provider Overview

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

If you’re unfamiliar with Kubernetes terminology, see the Kubernetes documentation .

This article describes how the Kubernetes provider works and how it differs from other providers in Spinnaker. If you’re unfamiliar with Kubernetes terminology, see the Kubernetes documentation .

The manifest-based approach

The Kubernetes provider combines the strengths of Kubernetes’s declarative infrastructure management with Spinnaker’s workflow engine for imperative steps when you need them. You can fully specify all your infrastructure in the native Kubernetes manifest format but still express, for example, a multi-region canary-driven rollout.

Oracle Cloud

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

For more information about Oracle Cloud or any of the terms used below, please consult Oracle Cloud Infrastructure Documentation .

Resource mapping

Account

The Oracle Cloud provider in Spinnaker maps a Spinnaker Account to an Oracle Cloud Infrastructure user in Oracle Cloud Infrastructure (OCI). Spinnaker authenticates itself with Oracle Cloud using OCI user credentials - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an OCI Load Balancer .

The OCI Load Balancing service offers a load balancer with your choice of a public or private IP address, and provisioned bandwidth. The essential components for load balancing include: