Catalog update [sailoperator] [v4.14,v4.15,v4.16,v4.17,v4.18,v4.19,v4.20,v4.21]

[openshift-service-mesh-bot]

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

New Submissions

• Are you familiar with our contribution guidelines?
• Have you packaged and deployed your Operator for Operator Framework?
• Have you tested your Operator with all Custom Resource Definitions?
• Have you tested your Operator in all supported installation modes?
• Have you considered whether you want to use semantic versioning order?
• Is your submission signed?
• Is operator icon set?

Updates to existing Operators

• Did you create a ci.yaml file according to the update instructions?
• Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
• Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
• Have you tested an update to your Operator when deployed via OLM?
• Is your submission signed?

Your submission should not

• Modify more than one operator
• Modify an Operator you don't own
• Rename an operator - please remove and add with a different name instead
• Modify any files outside the above-mentioned folders
• Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

1. Description about 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

• Human-readable name and 1-liner description about your Operator
• Valid category name¹
• One of the pre-defined capability levels²
• Links to the maintainer, source code and documentation
• Example templates for all Custom Resource Definitions intended to be used
• A quadratic logo

Remember that you can preview your CSV here.

--

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

² For more information see here

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runrtrjw
Start Time: 2026-05-05 06:46:56+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2026-05-05 06:47:04+00:00	5 seconds
✔️	acquire-lease	2026-05-05 06:47:17+00:00	5 seconds
✔️	set-github-started-label	2026-05-05 06:47:29+00:00	11 seconds
✔️	set-github-status-pending	2026-05-05 06:47:29+00:00	7 seconds
✔️	set-env	2026-05-05 06:47:45+00:00	6 seconds
✔️	clone-repository-base	2026-05-05 06:47:54+00:00	a minute
✔️	clone-repository	2026-05-05 06:47:54+00:00	a minute
✔️	detect-changes	2026-05-05 06:49:20+00:00	2 minutes
✔️	check-permissions	2026-05-05 06:51:09+00:00	19 seconds
✔️	set-github-pr-title	2026-05-05 06:51:09+00:00	7 seconds
✔️	content-hash	2026-05-05 06:51:10+00:00	24 seconds
✔️	static-tests	2026-05-05 06:51:10+00:00	2 minutes
✔️	read-config	2026-05-05 06:51:10+00:00	15 seconds
✔️	certification-project-check	2026-05-05 06:51:10+00:00	20 seconds
✔️	get-organization	2026-05-05 06:51:11+00:00	34 seconds
✔️	get-pyxis-certification-data	2026-05-05 06:53:23+00:00	12 seconds
✔️	get-supported-versions	2026-05-05 06:53:37+00:00	18 seconds
✔️	validate-catalog-format	2026-05-05 06:53:37+00:00	a minute
✔️	get-ci-results-attempt	2026-05-05 06:53:55+00:00	8 seconds
✔️	preflight-trigger	2026-05-05 06:54:05+00:00	10 seconds
✔️	get-ci-results	2026-05-05 06:54:18+00:00	7 seconds
✔️	build-fragment-images	2026-05-05 06:55:07+00:00	2 minutes
❔	build-fbc-index-images	2026-05-05 06:57:06+00:00	an hour

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/4e3411f7cc04368467ba398c87c933c4

Troubleshooting

Please refer to the troubleshooting guide.

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

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runzf4tl
Start Time: 2026-05-06 12:57:23+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2026-05-06 12:57:24+00:00	6 seconds
✔️	acquire-lease	2026-05-06 12:57:33+00:00	5 seconds
✔️	set-github-started-label	2026-05-06 12:57:41+00:00	11 seconds
✔️	set-github-status-pending	2026-05-06 12:57:41+00:00	8 seconds
✔️	set-env	2026-05-06 12:57:55+00:00	6 seconds
✔️	clone-repository	2026-05-06 12:58:06+00:00	a minute
✔️	clone-repository-base	2026-05-06 12:58:07+00:00	a minute
✔️	detect-changes	2026-05-06 12:59:27+00:00	2 minutes
✔️	set-github-pr-title	2026-05-06 13:01:18+00:00	9 seconds
✔️	check-permissions	2026-05-06 13:01:18+00:00	19 seconds
✔️	read-config	2026-05-06 13:01:19+00:00	20 seconds
✔️	static-tests	2026-05-06 13:01:20+00:00	2 minutes
✔️	content-hash	2026-05-06 13:01:20+00:00	27 seconds
✔️	certification-project-check	2026-05-06 13:01:21+00:00	38 seconds
✔️	get-organization	2026-05-06 13:01:22+00:00	33 seconds
✔️	get-pyxis-certification-data	2026-05-06 13:03:33+00:00	13 seconds
✔️	get-supported-versions	2026-05-06 13:03:47+00:00	19 seconds
✔️	validate-catalog-format	2026-05-06 13:03:47+00:00	2 minutes
✔️	get-ci-results-attempt	2026-05-06 13:04:07+00:00	7 seconds
✔️	preflight-trigger	2026-05-06 13:04:16+00:00	9 seconds
✔️	get-ci-results	2026-05-06 13:04:28+00:00	8 seconds
✔️	build-fragment-images	2026-05-06 13:05:19+00:00	2 minutes
✔️	build-fbc-index-images	2026-05-06 13:07:24+00:00	44 minutes
❌	merge-pr	2026-05-06 13:51:23+00:00	14 seconds

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

❌ Not merged

PR cannot be merged for the following reasons: Pull request redhat-openshift-ecosystem/community-operators-prod#9615 is not mergeable: the merge commit cannot be cleanly created.

Troubleshooting

Please refer to the troubleshooting guide.

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

[openshift-ci]

PR needs rebase.

Details

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.