search

redhat-openshift-ecosystem / community-operators-prod

community-operators metadata backing OpenShift OperatorHub
Apache License 2.0
103 stars 527 forks source link

Catalog update [v4.13,v4.14,v4.17,v4.16,v4.15,v4.18] #5275

Open zdtsw opened 4 days ago

zdtsw commented 4 days ago

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.

New Submissions

Your submission should not

Operator Description must contain (in order)

  1. [ ] Description of the managed Application and where to find more information
  2. [ ] Features and capabilities of your Operator and how to use it
  3. [ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

Remember that you can preview your CSV here.

--

1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need

2 For more information see here

zdtsw commented 4 days ago

FYI @VaishnaviHire @lburgazzoli

zdtsw commented 4 days ago

mark it as a draft, no need merge it now, only as preparation

rh-operator-bundle-bot commented 4 days ago

Pipeline Summary

Pipeline: operator-hosted-pipeline PipelineRun: operator-hosted-pipeline-run2nmk6 Start Time: 2024-10-02 15:45:13+00:00

Tasks

Status Task Start Time Duration
:heavy_check_mark: get-pr-number 2024-10-02 15:45:15+00:00 6 seconds
:heavy_check_mark: acquire-lease 2024-10-02 15:45:27+00:00 6 seconds
:heavy_check_mark: set-github-started-label 2024-10-02 15:45:38+00:00 10 seconds
:heavy_check_mark: set-github-status-pending 2024-10-02 15:45:50+00:00 7 seconds
:heavy_check_mark: set-env 2024-10-02 15:46:01+00:00 6 seconds
:heavy_check_mark: clone-repository 2024-10-02 15:46:11+00:00 41 seconds
:heavy_check_mark: clone-repository-base 2024-10-02 15:46:11+00:00 43 seconds
:heavy_check_mark: detect-changes 2024-10-02 15:46:58+00:00 53 seconds
:heavy_check_mark: check-permissions 2024-10-02 15:47:54+00:00 48 seconds
:heavy_check_mark: set-github-pr-title 2024-10-02 15:48:44+00:00 8 seconds
:heavy_check_mark: read-config 2024-10-02 15:48:56+00:00 36 seconds
:heavy_check_mark: resolve-pr-type 2024-10-02 15:49:35+00:00 7 seconds
:heavy_check_mark: validate-catalog-format 2024-10-02 15:49:46+00:00 41 seconds
:heavy_check_mark: build-fragment-images 2024-10-02 15:50:29+00:00 a minute
:heavy_check_mark: content-hash 2024-10-02 15:51:35+00:00 32 seconds
:heavy_check_mark: certification-project-check 2024-10-02 15:52:10+00:00 35 seconds
:heavy_check_mark: get-organization 2024-10-02 15:52:48+00:00 49 seconds
:heavy_check_mark: get-pyxis-certification-data 2024-10-02 15:53:39+00:00 41 seconds
:heavy_check_mark: static-tests 2024-10-02 15:54:25+00:00 40 seconds
:heavy_check_mark: static-tests-results 2024-10-02 15:55:12+00:00 16 seconds
:heavy_check_mark: merge-registry-credentials 2024-10-02 15:55:33+00:00 15 seconds
:heavy_check_mark: digest-pinning 2024-10-02 15:55:52+00:00 46 seconds
:heavy_check_mark: verify-pinned-digest 2024-10-02 15:56:41+00:00 7 seconds
:heavy_check_mark: dockerfile-creation 2024-10-02 15:56:50+00:00 33 seconds
:heavy_check_mark: build-bundle 2024-10-02 15:57:30+00:00 41 seconds
:heavy_check_mark: get-supported-versions 2024-10-02 15:58:18+00:00 42 seconds
:heavy_check_mark: build-fbc-index-images 2024-10-02 15:59:05+00:00 11 minutes
:heavy_check_mark: get-ci-results-attempt 2024-10-02 16:10:06+00:00 18 seconds
:heavy_check_mark: preflight-trigger 2024-10-02 16:10:25+00:00 18 seconds
:heavy_check_mark: get-ci-results 2024-10-02 16:10:44+00:00 16 seconds
:heavy_check_mark: link-pull-request-with-open-status 2024-10-02 16:11:03+00:00 7 seconds
:heavy_check_mark: merge-pr 2024-10-02 16:11:14+00:00 42 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/0a344f8f69e0b5d2412dabb17d87f74d

❌ Not merged

PR cannot be merged for the following reasons: Pull Request is still a draft (mergePullRequest)

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

zdtsw commented 4 days ago

@Allda could you help me understand: after onboarding (this PR) what will need for the next release? assume we are going to have a 2.19.0 release, according to https://olm.operatorframework.io/docs/advanced-tasks/catalog-update-formulary/#fbc we only need to run something like yq eval 'select(.schema=="olm.channel" and .name == "fast").entries += [{"name" : "opendatahub-operator.v2.19.0", "replaces": "opendatahub-operator.v2.18.2", "skipRange": "'>=1.0.0 <2.19.0", "skips": ["opendatahub-operator.v2.9.0"]}]' catalogs/v${version}/opendatahub-operator/catalog.yaml => here version will be a loop of 4.12 4.13 4.14 4.15.4.16 ? is that enough? what about these schema: olm.bundle entries with olm.bundle.object, how do they get updated ? or am i totally in the wrong direction, that we should change catalog-templates/* instead then run opm to generate catalog.yaml

mporrato commented 3 days ago

@zdtsw once this is merged, to publish a new bundle you will have to submit a PR to add the new bundle (i.e.: operators/opendatahub-operator/2.19.0) just like you used to do before. Once the PR is merged, you can submit a second PR to update the catalogs: you do this by editing the catalog-template files depending on which channels you want to make the new bundle available and run make catalogs to automatically update the files under catalogs/: for example, for 2.19.0 you may want to add something like

  - name: opendatahub-operator.v2.19.0
    replaces: opendatahub-operator.v2.18.2
    skipRange: '>=1.0.0 <2.19.0'
    skips:
    - opendatahub-operator.v2.9.0

to your olm.channel sections and

- image: quay.io/community-operator-pipeline-prod/opendatahub-operator:2.19.0
  schema: olm.bundle

to the root level olm.template.basic section. BTW, you probably should include the Makefile in this PR. Let me know if this is not clear enough.