Spinnaker Artifacts

Internal

• Spinnaker Concepts

Overview

Artifacts

https://spinnaker.io/docs/setup/other_config/artifacts/

https://spinnaker.io/docs/reference/artifacts-legacy/

Artifacts are external resources that can be referred from Spinnaker and deployed. Artifacts can be defined while configuring stages, such as Bake (Manifest). Artifacts can be specified in-line, in text format, within the stages themselves, or. in case they are available externally, they are accessed via artifact accounts. An artifact account is a source of artifacts for Spinnaker. Each artifact account (usually a registry or repository of some sort) must be configured in Spinnaker.

GitHub File/Directory Artifacts

https://spinnaker.io/docs/setup/other_config/artifacts/github/

Use a "github" account, when the artifact is needed.

Helm Chart Artifacts

Use a Helm repository account, when the artifact is needed.

Container Image Artifacts

https://spinnaker.io/docs/setup/install/providers/docker-registry/

S3 Artifacts

https://spinnaker.io/docs/reference/ref-artifacts/types/s3-object/

https://spinnaker.io/docs/setup/other_config/artifacts/s3/

S3 artifacts can be used to trigger pipelines, or they can be declared in the artifact sections of various pipeline stages such as Deploy (Manifest) or Deploy. To be accessible in the trigger or within the pipeline, there should be an S3 "account" the S3 object should be accessible under.