Skip to content

AM0003

Jump to bottom
sugarraysam edited this page Dec 28, 2021 · 2 revisions

operator_name

Problematic configuration:

1. operatorName does not match either csv.Name or csv.Replaces

# addon.yaml
operatorName: rhods-operator

# manifests/rhods-operator.X.Y.Z.clusterserviceversion.yaml (bundle X.Y.Z)
metadata:
  name: invalid.X.Y.Z
spec:
  replaces: invalid.X.Y.Z

The operatorName has to match the first part of both metadata.name and spec.replaces for all CSV of all bundles.

2. operatorName does not match the package bundle annotation

# addon.yaml
operatorName: rhods-operator

# metadata/annotations.yaml (bundle X.Y.Z)
annotations:
  operators.operatorframework.io.bundle.package.v1: invalid

For all bundles, the operators.operatorframework.io.bundle.package.v1 has to match the value of operatorName. This is how OLM can find and install the desired operator from your catalog.

Correct configuration:

# addon.yaml
operatorName: rhods-operator

# manifests/rhods-operator.X.Y.Z.clusterserviceversion.yaml (bundle X.Y.Z)
metadata:
  name: rhods-operator.X.Y.Z
spec:
  replaces: rhods-operator.X.Y.Z

# metadata/annotations.yaml (bundle X.Y.Z)
annotations:
  operators.operatorframework.io.bundle.package.v1: rhods-operator
  • operatorName matches first part of metadata.name and spec.replaces in CSV manifest
  • operatorName matches the operators.operatorframework.io.bundle.package.v1 bundle annotation

Related resources:

Clone this wiki locally