MinKubeVersion in the OLM ClusterServiceVersion doesn't match the actual requirement

[cm3lindsay]

Describe the bug As part of knatives release schedule, supported Kubernetes versions are regularly changed. https://github.com/knative/community/blob/main/mechanics/RELEASE-SCHEDULE.md

However when knative bumps the minimum k8s version in https://github.com/knative/pkg (such as this PR https://github.com/knative/pkg/pull/2832) the minKubeVersion in clusterserviceversion for the matching release of knative-operator isn't being updated to match. Currently its hardcoded to 1.22. This results in operator-lifecylce-manager thinking the release is supported on the current kubernetes cluster and updates it.

Because operator-lifecycle-manager doesn't support downgrades, it leaves users with a broken knative-operator.

Expected behavior The minimum k8s version in the clusterserviceversion should match the actual minimum k8s version required by the knative-operator (1.26 in the case of knative 1.12).

To Reproduce Install the operator using operator-lifecycle-manager on a K8S cluster running 1.25. Knative-operator will fail to start. The same situation happens when running an existing install, then Knative release a new version that removes support for previous versions.

Knative release version 1.11 / 1.12

In theory the problem should have existed since 1.8.

Additional context This issue can easily break an existing deployment of knative-operator for users.

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[ghost]

/remove-lifecycle stale

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[knative-prow[bot]]

@lindsaygrace: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

/remove-lifecycle stale

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.