Updating existing Operators

Updating operator version

Operator version update can be done by creating new directory with version name in operator dir without 'v'. For example updating aqua operator from 1.0.0 to 1.0.1

$ tree community-operators/aqua/ -d
community-operators/aqua/
├── 0.0.1
├── 0.0.2
├── 1.0.0
├── 1.0.1

Minor (cosmetics) changes

There are some case when only some minor changes to the existing operator are needed (like description update or an update of icon). In this case pipeline will set corresponding label and automatically handle such case.

Allowed changes

• Only changes in csv (*.clusterserviceversion.yaml) are allowed
• List of allowed tag changes in csv
  • spec.description
  • spec.DisplayName
  • spec.icon
  • metadata.annotations.description
  • metadata.annotations.alm-examples

Operator versioning strategy

Sometimes it is needed to change how operator versions are built in to the index. This can be controlled by ci.yaml file. More info

Reviewers update

While operator is involving over a time, some time it is needed to change reviewers. This can be controlled by ci.yaml file. More info