API Markers

This document describes code markers supported by the SDK.

ClusterServiceVersion markers

This section details ClusterServiceVersion (CSV) code markers and lists available markers.

Note: CSV markers can only be used in Go Operator projects. Annotations for Ansible and Helm Operator projects will be added in the future.

Usage

All markers have a +operator-sdk:gen-csv prefix, denoting that they’re parsed while executing operator-sdk generate kustomize manifests.

Paths

Paths are dot-separated string hierarchies with the above prefix that map to CSV spec field names.

Example: +operator-sdk:gen-csv:customresourcedefinitions.specDescriptors.displayName="Pod Count"

customresourcedefinitions

• customresourcedefinitions: child path token
  • displayName: quoted string or string literal
  • resources: quoted string or string literal, in the format "kind,version,\"name\"" or `kind,version,"name"` , where kind, version, and name are fields in each CSV resources entry
  • specDescriptors, statusDescriptors: bool, or child path token
    • displayName: quoted string or string literal
    • x-descriptors: quoted string or string literal comma-separated list of x-descriptor UI hints.

NOTES

• specDescriptors and statusDescriptors with a value of true is required for each field to be included in their respective customresourcedefinitions CSV fields. See the examples below.
• customresourcedefinitions top-level kind, name, and version fields are parsed from API code.
• All description fields are parsed from type declaration and struct type field comments.
• path is parsed out of a field’s JSON tag and merged with parent field path’s in dot-hierarchy notation.

Examples

These examples assume Memcached, MemcachedSpec, and MemcachedStatus are the example projects’ kind, spec, and status.

1. Set a display name for a customresourcedefinitions kind entry:

// +operator-sdk:gen-csv:customresourcedefinitions.displayName="Memcached App"
type Memcached struct {
    metav1.TypeMeta   `json:",inline"`
    metav1.ObjectMeta `json:"metadata,omitempty"`
    Spec   MemcachedSpec   `json:"spec,omitempty"`
    Status MemcachedStatus `json:"status,omitempty"`
}

1. Set displayName, path, x-descriptors, and description on a field for a customresourcedefinitions.specDescriptors entry:

type MemcachedSpec struct {
    // Size is the size of the memcached deployment. <-- This will become Size's specDescriptors.description.
    // +operator-sdk:gen-csv:customresourcedefinitions.specDescriptors=true
    // +operator-sdk:gen-csv:customresourcedefinitions.specDescriptors.displayName="Pod Count"
    // +operator-sdk:gen-csv:customresourcedefinitions.specDescriptors.x-descriptors="urn:alm:descriptor:com.tectonic.ui:podCount,urn:alm:descriptor:io.kubernetes:custom"
    Size int32 `json:"size"` // <-- Size's specDescriptors.path is inferred from this JSON tag.
}

1. Let the SDK infer all unmarked paths on a field for a customresourcedefinitions.specDescriptors entry:

type MemcachedSpec struct {
    // Size is the size of the memcached deployment.
    // +operator-sdk:gen-csv:customresourcedefinitions.specDescriptors=true
    Size int32 `json:"size"`
}

The SDK uses the Size fields’ json tag name as path, Size as displayName, and field comments as description.

The SDK also checks path elements against a list of well-known path to x-descriptor string mappings and either uses a match as x-descriptors, or does not set x-descriptors. Supported mappings:

Spec x-descriptors

Status x-descriptors

NOTE: any x-descriptor that ends in : will not be inferred by path element, ex. urn:alm:descriptor:io.kubernetes:. Use the x-descriptors marker if you want to enable one for your type.

1. A comprehensive example:

• Infer path, description, displayName, and x-descriptors for specDescriptors and statusDescriptors entries.
• Create three resources entries each with kind, version, and name values.

// Represents a cluster of Memcached apps
// +operator-sdk:gen-csv:customresourcedefinitions.displayName="Memcached App"
// +operator-sdk:gen-csv:customresourcedefinitions.resources="Deployment,v1,\"memcached-operator\""
// +operator-sdk:gen-csv:customresourcedefinitions.resources=`Service,v1,"memcached-operator"`
type Memcached struct {
    metav1.TypeMeta   `json:",inline"`
    metav1.ObjectMeta `json:"metadata,omitempty"`
    Spec   MemcachedSpec   `json:"spec,omitempty"`
    Status MemcachedStatus `json:"status,omitempty"`
}
type MemcachedSpec struct {
    Pods MemcachedPods `json:"pods"`
}
type MemcachedStatus struct {
    Pods MemcachedPods `json:"podStatuses"`
}
type MemcachedPods struct {
    // Size is the size of the memcached deployment.
    // +operator-sdk:gen-csv:customresourcedefinitions.specDescriptors=true
    // +operator-sdk:gen-csv:customresourcedefinitions.statusDescriptors=true
    Size int32 `json:"size"`
}

The generated customresourcedefinitions will look like:

customresourcedefinitions:
  owned:
  - description: Represents a cluster of Memcached apps
    displayName: Memcached App
    kind: Memcached
    name: memcacheds.cache.example.com
    version: v1alpha1
    resources:
    - kind: Deployment
      name: A Kubernetes Deployment
      version: v1
    - kind: ReplicaSet
      name: A Kubernetes ReplicaSet
      version: v1beta2
    - kind: Pod
      name: A Kubernetes Pod
      version: v1
    specDescriptors:
    - description: The desired number of member Pods for the deployment.
      displayName: Size
      path: pods.size
      x-descriptors:
      - 'urn:alm:descriptor:com.tectonic.ui:podCount'
    statusDescriptors:
    - description: The desired number of member Pods for the deployment.
      displayName: Size
      path: podStatuses.size
      x-descriptors:
      - 'urn:alm:descriptor:com.tectonic.ui:podStatuses'
      - 'urn:alm:descriptor:com.tectonic.ui:podCount'

Last modified July 8, 2020: docs: OLM integration docs reference new commands (new and legacy CLI) (#3320) (ec03835e)