Ali Ok
Ali Ok
We can use Operator SDK cli to generate CSV also for non-Operator-SDK operators. I've done some experiments here: https://github.com/aliok/eventing-operator/tree/olm-experiments-bundle Filed 2 tickets: 1. https://github.com/operator-framework/operator-sdk/issues/2266 2. https://github.com/operator-framework/operator-sdk/issues/2267 and objected https://github.com/operator-framework/operator-sdk/pull/2249 which...
Update: I am still helping Operator SDK team to make the CLI supporting the cases we need at Knative operators: https://github.com/operator-framework/operator-sdk/pull/2511 We're very close to have tooling ready for our...
https://github.com/operator-framework/operator-sdk/pull/2511 has lots of progress. Once that PR is merged and we fix https://github.com/knative/eventing-operator/issues/128, we can use operator-sdk as is to generate OLM metadata.
/label good-first-issue
@houshengbo I understand the reasoning behind the separate version controller. It doesn't make sense to delete old CRs and create new CRs within the eventing operator. The operator is managing...
For future reference, this ticket was closed as the discussion moved from here to Knative [operator upgrade design doc](https://docs.google.com/document/d/1HEH9b4XWqFXtitAeHvCzymEG8-dtKH5y/edit)
/hold Hold until https://github.com/operator-framework/community-operators/pull/1337 is merged
If we do this improvement, we can use these templates as-is in Backstage.
/reopen /remove-lifecycle stale