Kubernetes CRD Extensions

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

Spinnaker Extension Points for Custom Resource Definitions

At Google, we’ve built extension points for deep CRD integrations within Spinnaker.

This work has allowed us to support the following features within Spinnaker:

Custom models for representing CRDs as spinnakerKinds
Deploying CRDs with custom Spinnaker artifact types
Custom Kubernetes API versions
Custom Spinnaker naming strategies
Per-account, custom Spinnaker UIs that can run alongside the existing Kubernetes UIs

This guide is for developers who want to duplicate this functionality for their CRDs. It also exists as an explanation of certain code paths within Spinnaker which include hooks with no current corresponding open-source implementations.

Writing a New Stage

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

Overview

To create a new stage, you need to make changes in the monorepo to orca to implement the logic of the stage, and the front-end changes in deck to implement the UI. Depending on what the stage does, you may need to implement new cloud provider-specific logic in clouddriver and/or expose new APIs in gate as well.

This doc currently only covers the backend changes made to orca.

Backend (orca)

For the backend, you need to define:

Extending Spinnaker on Spinnaker

Kubernetes CRD Extensions

Spinnaker Extension Points for Custom Resource Definitions

Writing a New Stage

Overview

Backend (orca)