Devfile registry operator pre-release to OperatorHub

[michael-valdron]

Which area/kind this issue is related to?

/area registry
/area releng

Issue Description

In #410, we plan to make our first release of the registry operator available on OperatorHub for consumers. To ensure early adopters are ready to ship when this release becomes available, it would be necessary to also provide pre-releases.

Resolve #1106 to ensure no problems with publishing.

Acceptance Criteria

• Required documentation for publication https://k8s-operatorhub.github.io/community-operators/packaging-operator/#provide-information-about-your-operator
  • What the managed application is about and where to find more information
  • The features of your Operator and how to use it
  • Any manual steps required to fulfill pre-requisites for running/installing your Operator
• Cut pre-release number for registry operator
• Ensure bundle files are up to date and placed under the following directory structure within a folk of k8s-operatorhub/community-operators: https://k8s-operatorhub.github.io/community-operators/packaging-operator/#create-a-release
• Create a PR of these change to the folk within the k8s-operatorhub/community-operators repository and merge once approved

[michael-valdron]

Cut pre-release number for registry operator

I think we should start with 0.1.0, increment on minor until our first release 1.0.0.

[michael-valdron]

Add minimal documentation for publication to OperatorHub

[michael-valdron]

Add minimal documentation for publication to OperatorHub

Documentation acceptance criteria has been included.

[michael-valdron]

Begun prep work for pre-release. Updated maintainers, CR descriptors, and set version fields to 0.1.0.

[michael-valdron]

Waiting for devfile/registry-operator#45 to merge: #1106 (comment)

[michael-valdron]

Rebased prep changes with recent changes from devfile/registry-operator#45 & devfile/registry-operator#46

[michael-valdron]

It seems that kustomize has an ongoing bug which prevents us from using it to build off custom resources which kind ends with List: kubernetes-sigs/kustomize#5042

For this issue, I cannot generate the examples of ClusterDevfileRegistriesList and DevfileRegistriesList under the CSV, I can continue without these and open a new issue for this separately to fix once kubernetes-sigs/kustomize#5042 is resolved.

Will try manually entering the examples of ClusterDevfileRegistriesList and DevfileRegistriesList at this time.

[michael-valdron]

Part 1 of this issue is ready for review: devfile/registry-operator#47

[michael-valdron]

Part 2: Cutting the new release v0.1.0 in the registry operator repository
Part 3: Begin the process of publication to OperatorHub by opening a PR to k8s-operatorhub/community-operators with the version bundle

[michael-valdron]

New release v0.1.0 has been cut on GitHub.

Part 3: Begin the process of publication to OperatorHub by opening a PR to k8s-operatorhub/community-operators with the version bundle

This part is being blocked by #1251 due to OLM validation passing being required for publication to OperatorHub.

[michael-valdron]

Contributing doc for OperatorHub: https://github.com/operator-framework/community-operators/blob/master/docs/contributing-via-pr.md

[rm3l]

Candidate for demo at the end of the Sprint in which it will be completed.

[michael-valdron]

devfile/registry-operator#49 (comment)

[michael-valdron]

Keeping status blocked to include #1028 under new release cut.

[michael-valdron]

New release v0.1.1 has been cut on GitHub.

Part 3: Begin the process of publication to OperatorHub by opening a PR to k8s-operatorhub/community-operators with the version bundle

Starting part 3 to publish to OperatorHub.

[michael-valdron]

Opened a PR with current version's bundle:
k8s-operatorhub/community-operators#3287

Experiencing an failing check which seems to be flagging a missing field which is not missing from the CSV file: k8s-operatorhub/community-operators#3287 (comment)

[michael-valdron]

Opened a PR with current version's bundle: k8s-operatorhub/community-operators#3287

Experiencing an failing check which seems to be flagging a missing field which is not missing from the CSV file: k8s-operatorhub/community-operators#3287 (comment)

Opened Q&A discussion about this problem: k8s-operatorhub/community-operators#3294

[michael-valdron]

Opened a PR with current version's bundle: k8s-operatorhub/community-operators#3287
Experiencing an failing check which seems to be flagging a missing field which is not missing from the CSV file: k8s-operatorhub/community-operators#3287 (comment)

Opened Q&A discussion about this problem: k8s-operatorhub/community-operators#3294

Update: I received feedback on this problem and found that categories was misspelled under the CSV 🤦. I have corrected this in devfile/registry-operator#52 and will cut a new patch version for the OperatorHub publication.

[michael-valdron]

There is a missing place to update the operator version: k8s-operatorhub/community-operators#3287 (comment)

Investigating this on the operator side.

[michael-valdron]

There is a missing place to update the operator version: k8s-operatorhub/community-operators#3287 (comment)

Investigating this on the operator side.

Opened PR for new patch changes: devfile/registry-operator#54

These changes will fully pass kiwi testing: https://github.com/k8s-operatorhub/community-operators/actions/runs/6487040924/job/17616540337

[michael-valdron]

PR to publish to OperatorHub.io is now ready for review: k8s-operatorhub/community-operators#3287

[michael-valdron]

Publication PR k8s-operatorhub/community-operators#3287 has now been merged and the registry operator is now published to OperatorHub.io: https://operatorhub.io/operator/registry-operator

Closing this issue.