CI pipeline prevents Minor Cosmetic Changes about community-operators

[wallrj]

Here are links and extracts from the documentation that I am referring to:

Updating your existing Operator

Unless of purely cosmetic nature, subsequent updates to your Operator should result in new bundle directories being added, containing an updated CSV as well as copied, updated and/or potentially newly added CRDs. Within your new CSV, update the spec.version field to the desired new semantic version of your Operator.

Operator deploy tests (lemon/orange) test failures

All operator versions are already in catalog
You are trying to edit an existing operator version. It is not recommended. But there are some exceptions, where you just edit some description or link. In this case, repository maintainers can set appropriate labels to override such errors and approve release pipeline action to overwrite an existing operator.

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.

[wallrj]

And I suppose the reason for not allowing e.g. ServiceAccount changes to existing bundles is that OLM would have no way to upgrade users who had already installed the existing bundle.
Here for example. The cert-manager 1.6.1 bundle will already be wide spread use. So if I change the ServiceAccount for 1.6.1 and if the CI allowed that, and if those updated packages got published to the OLM catalogue then we'd end up with users with slightly different OLM installations of cert-manager 1.6.1, which will cause confusion at best and may cause upgrade headaches at worst.

[J0zi]

@wallrj in case single version change, we are checking if change is cosmetic
In case of multiple versions change, we are creating new bundles again, but old bundles are still present and valid for previous versions of catalog.
Service account issue is just output from the newest operator-sdk. It wasn't there in older version. @camilamacedo86 already explained in #722 (comment)

[camilamacedo86]

HI @wallrj,

You must solve the SA issue. Allow this configuration in the bundle was a bug since OLM will be unable to handle it.
So, I'd recommend you check all bundles against the latest SDK version 1.17.0 and the command operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework and fix the previous ones as well if that is the case. Please, create a PR for each bundle version if you need to do that.

c/c @mvalarh @J0zi

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 30 days since being marked as stale.