operator vault-config-operator (0.8.30) #6197

raffaelespazzoli · 2025-03-17T17:30:02Z

New Submissions

Has you operator nested directory structure?
Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
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?
Is your submission signed?

Updates to existing Operators

Is your new CSV pointing to the previous version with the replaces property?
Is your new CSV referenced in the appropriate channel defined in the package.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
Submit operators to both upstream-community-operators and community-operators at once
Modify any files outside the above mentioned folders
Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

Description about the managed Application and where to find more information
Features and capabilities of your Operator and how to use it
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 a PR against this repo and explain your need
² For more information see here

Signed-off-by: raffaelespazzoli <[email protected]>

rh-operator-bundle-bot · 2025-03-17T17:41:27Z

Static test results

Status	Check	Message
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value vault-config-operator.v0.8.30: owned CRD "azuresecretengineconfigs.redhatcop.redhat.io" has an empty description
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : The "operatorhub" validator is deprecated; for equivalent validation use "operatorhub/v2", "standardcapabilities" and "standardcategories" validators
⚠️	check_using_fbc	File Based Catalog (FBC) is a new way to manage operator metadata. This operator does not use FBC. Consider migrating for better maintainability.

rh-operator-bundle-bot · 2025-03-17T18:20:20Z

Test artifacts: https://gist.github.com/rh-operator-bundle-bot/4a63c4f9e106a0ee1d4fc66ae795ef25

rh-operator-bundle-bot · 2025-03-17T18:20:55Z

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-rundscgt
Start Time: 2025-03-17 17:30:06+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2025-03-17 17:30:06+00:00	40 seconds
✔️	acquire-lease	2025-03-17 17:30:49+00:00	7 seconds
✔️	set-github-started-label	2025-03-17 17:31:01+00:00	37 seconds
✔️	set-github-status-pending	2025-03-17 17:31:01+00:00	8 seconds
✔️	set-env	2025-03-17 17:31:40+00:00	6 seconds
✔️	clone-repository	2025-03-17 17:31:51+00:00	47 seconds
✔️	clone-repository-base	2025-03-17 17:31:51+00:00	46 seconds
✔️	detect-changes	2025-03-17 17:32:41+00:00	a minute
✔️	yaml-lint	2025-03-17 17:33:46+00:00	47 seconds
✔️	check-permissions	2025-03-17 17:34:35+00:00	41 seconds
✔️	set-github-pr-title	2025-03-17 17:35:19+00:00	7 seconds
✔️	read-config	2025-03-17 17:35:31+00:00	44 seconds
✔️	resolve-pr-type	2025-03-17 17:36:17+00:00	6 seconds
✔️	apply-test-waivers	2025-03-17 17:36:26+00:00	41 seconds
✔️	content-hash	2025-03-17 17:37:08+00:00	40 seconds
✔️	certification-project-check	2025-03-17 17:37:51+00:00	46 seconds
✔️	get-organization	2025-03-17 17:38:41+00:00	48 seconds
✔️	get-pyxis-certification-data	2025-03-17 17:39:31+00:00	49 seconds
✔️	static-tests	2025-03-17 17:40:22+00:00	a minute
✔️	merge-registry-credentials	2025-03-17 17:41:32+00:00	17 seconds
✔️	digest-pinning	2025-03-17 17:41:51+00:00	48 seconds
✔️	verify-pinned-digest	2025-03-17 17:42:42+00:00	7 seconds
✔️	dockerfile-creation	2025-03-17 17:42:51+00:00	42 seconds
✔️	build-bundle	2025-03-17 17:43:34+00:00	a minute
✔️	make-bundle-repo-public	2025-03-17 17:45:05+00:00	6 seconds
✔️	get-supported-versions	2025-03-17 17:45:13+00:00	44 seconds
✔️	add-bundle-to-index	2025-03-17 17:45:57+00:00	3 minutes
✔️	make-index-repo-public	2025-03-17 17:49:54+00:00	7 seconds
✔️	get-ci-results-attempt	2025-03-17 17:50:02+00:00	18 seconds
✔️	preflight-trigger	2025-03-17 17:50:21+00:00	29 minutes
❌	evaluate-preflight-result	2025-03-17 18:19:29+00:00	52 seconds

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

Troubleshooting

Please refer to the troubleshooting guide.

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

raffaelespazzoli · 2025-03-17T18:39:10Z

hello, can someone help me understand what the issue is?
from the log, this seems relevant:

[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,342 [operator-cert] INFO Test: ScorecardBasicSpecCheck, allowed: True
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,342 [operator-cert] INFO Test: ScorecardOlmSuiteCheck, allowed: True
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] DEBUG Skipping test: ValidateOperatorBundle
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Test: ValidateOperatorBundle, allowed: False
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] DEBUG Skipping test: RequiredAnnotations
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Test: RequiredAnnotations, allowed: False
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Test: DeployableByOLM, allowed: True
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Overall status: False
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Result by category: {'passed': 2, 'failed': 0, 'errors': 1}

but it does not explain why there is an error.

tomasbakk · 2025-03-18T09:41:39Z

hello, can someone help me understand what the issue is? from the log, this seems relevant:

[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,342 [operator-cert] INFO Test: ScorecardBasicSpecCheck, allowed: True
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,342 [operator-cert] INFO Test: ScorecardOlmSuiteCheck, allowed: True
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] DEBUG Skipping test: ValidateOperatorBundle
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Test: ValidateOperatorBundle, allowed: False
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] DEBUG Skipping test: RequiredAnnotations
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Test: RequiredAnnotations, allowed: False
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Test: DeployableByOLM, allowed: True
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Overall status: False
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Result by category: {'passed': 2, 'failed': 0, 'errors': 1}

but it does not explain why there is an error.

Hello @raffaelespazzoli . The preflight test failed on the DeployableByOLM test. The test verifies if the operator could be deployed by OLM.

raffaelespazzoli · 2025-03-18T13:58:35Z

@tomasbakk what makes you say that the operator could not be deployed by OLM? We do that test on our side of the pipeline and it passed. Also from the logs:

[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Test: DeployableByOLM, allowed: True
[evaluate-preflight-result : evaluate-results] 2025-03-17 18:20:17,343 [operator-cert] INFO Overall status: False

it looks like the DeployableByOLM was true.
Finally if it failed trying to deploy via OLM, what was the error?

tomasbakk · 2025-03-19T09:31:29Z

@raffaelespazzoli The log you are referring to states whether particular test will be skipped or no. In this case, OLM test is not skipped during the pipeline run. Looking into artefacts from the preflight, we got: could not retrieve the object openshift-marketplace/vault-config-operator.v0.8.30. I will try to re-run the pipeline and check it, whether it warrants looking into it or it was a one-time error.

rh-operator-bundle-bot · 2025-03-19T09:42:49Z

Static test results

Status	Check	Message
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value vault-config-operator.v0.8.30: owned CRD "azuresecretengineconfigs.redhatcop.redhat.io" has an empty description
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : (vault-config-operator.v0.8.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : The "operatorhub" validator is deprecated; for equivalent validation use "operatorhub/v2", "standardcapabilities" and "standardcategories" validators
⚠️	check_using_fbc	File Based Catalog (FBC) is a new way to manage operator metadata. This operator does not use FBC. Consider migrating for better maintainability.

rh-operator-bundle-bot · 2025-03-19T10:20:46Z

Test artifacts: https://gist.github.com/rh-operator-bundle-bot/6ff34527b1f5ddad493d9e4bf5738b05

rh-operator-bundle-bot · 2025-03-19T10:23:29Z

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run74pq2
Start Time: 2025-03-19 09:31:37+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2025-03-19 09:31:41+00:00	8 seconds
✔️	acquire-lease	2025-03-19 09:31:58+00:00	8 seconds
✔️	set-github-started-label	2025-03-19 09:32:11+00:00	13 seconds
✔️	set-github-status-pending	2025-03-19 09:32:12+00:00	7 seconds
✔️	set-env	2025-03-19 09:32:31+00:00	9 seconds
✔️	clone-repository-base	2025-03-19 09:32:49+00:00	56 seconds
✔️	clone-repository	2025-03-19 09:32:49+00:00	54 seconds
✔️	detect-changes	2025-03-19 09:33:49+00:00	56 seconds
✔️	yaml-lint	2025-03-19 09:34:54+00:00	46 seconds
✔️	check-permissions	2025-03-19 09:35:42+00:00	40 seconds
✔️	set-github-pr-title	2025-03-19 09:36:28+00:00	7 seconds
✔️	read-config	2025-03-19 09:36:38+00:00	42 seconds
✔️	resolve-pr-type	2025-03-19 09:37:25+00:00	9 seconds
✔️	apply-test-waivers	2025-03-19 09:37:39+00:00	44 seconds
✔️	content-hash	2025-03-19 09:38:28+00:00	46 seconds
✔️	certification-project-check	2025-03-19 09:39:18+00:00	45 seconds
✔️	get-organization	2025-03-19 09:40:07+00:00	48 seconds
✔️	get-pyxis-certification-data	2025-03-19 09:40:58+00:00	48 seconds
✔️	static-tests	2025-03-19 09:41:48+00:00	a minute
✔️	merge-registry-credentials	2025-03-19 09:42:54+00:00	14 seconds
✔️	digest-pinning	2025-03-19 09:43:10+00:00	46 seconds
✔️	verify-pinned-digest	2025-03-19 09:43:59+00:00	7 seconds
✔️	dockerfile-creation	2025-03-19 09:44:08+00:00	42 seconds
✔️	build-bundle	2025-03-19 09:44:54+00:00	56 seconds
✔️	make-bundle-repo-public	2025-03-19 09:45:51+00:00	8 seconds
✔️	get-supported-versions	2025-03-19 09:46:01+00:00	42 seconds
✔️	add-bundle-to-index	2025-03-19 09:46:44+00:00	4 minutes
✔️	make-index-repo-public	2025-03-19 09:51:03+00:00	8 seconds
✔️	get-ci-results-attempt	2025-03-19 09:51:12+00:00	16 seconds
✔️	preflight-trigger	2025-03-19 09:51:28+00:00	28 minutes
✔️	evaluate-preflight-result	2025-03-19 10:19:59+00:00	48 seconds
✔️	get-ci-results	2025-03-19 10:20:48+00:00	7 seconds
✔️	link-pull-request-with-open-status	2025-03-19 10:20:56+00:00	8 seconds
✔️	add-bundle-to-fbc-dryrun	2025-03-19 10:21:04+00:00	44 seconds
✔️	merge-pr	2025-03-19 10:21:48+00:00	15 seconds
✔️	link-pull-request-with-merged-status	2025-03-19 10:22:06+00:00	7 seconds

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

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 · 2025-03-19T11:11:24Z

Pipeline Summary

Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-runcpwn9
Start Time: 2025-03-19 10:22:03+00:00

Tasks

Status	Task	Start Time	Duration
✔️	set-github-started-label	2025-03-19 10:22:07+00:00	9 seconds
✔️	set-github-status-pending	2025-03-19 10:22:07+00:00	7 seconds
✔️	set-env	2025-03-19 10:22:23+00:00	8 seconds
✔️	clone-repository-base	2025-03-19 10:22:36+00:00	a minute
✔️	clone-repository	2025-03-19 10:22:36+00:00	a minute
✔️	detect-changes	2025-03-19 10:23:41+00:00	54 seconds
✔️	read-config	2025-03-19 10:24:35+00:00	13 seconds
✔️	resolve-pr-type	2025-03-19 10:24:48+00:00	7 seconds
✔️	content-hash	2025-03-19 10:24:56+00:00	46 seconds
✔️	certification-project-check	2025-03-19 10:25:43+00:00	12 seconds
✔️	get-organization	2025-03-19 10:25:55+00:00	12 seconds
✔️	get-pyxis-certification-data	2025-03-19 10:26:07+00:00	17 seconds
✔️	copy-bundle-image-to-released-registry	2025-03-19 10:26:24+00:00	8 seconds
✔️	add-bundle-to-fbc	2025-03-19 10:26:32+00:00	47 seconds
✔️	get-supported-versions	2025-03-19 10:26:32+00:00	42 seconds
✔️	acquire-lease	2025-03-19 10:27:14+00:00	26 minutes
✔️	add-bundle-to-index	2025-03-19 10:53:32+00:00	16 minutes
❌	sign-index-image	2025-03-19 11:09:33+00:00	32 seconds

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

Troubleshooting

Please refer to the troubleshooting guide.

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

rh-operator-bundle-bot · 2025-03-19T12:48:58Z

Pipeline Summary

Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run5827g
Start Time: 2025-03-19 12:12:41+00:00

Tasks

Status	Task	Start Time	Duration
✔️	set-github-started-label	2025-03-19 12:12:41+00:00	10 seconds
✔️	set-github-status-pending	2025-03-19 12:12:42+00:00	7 seconds
✔️	set-env	2025-03-19 12:12:53+00:00	8 seconds
✔️	clone-repository-base	2025-03-19 12:13:01+00:00	45 seconds
✔️	clone-repository	2025-03-19 12:13:02+00:00	48 seconds
✔️	detect-changes	2025-03-19 12:13:51+00:00	a minute
✔️	read-config	2025-03-19 12:15:10+00:00	56 seconds
✔️	resolve-pr-type	2025-03-19 12:16:07+00:00	7 seconds
✔️	content-hash	2025-03-19 12:16:14+00:00	48 seconds
✔️	certification-project-check	2025-03-19 12:17:03+00:00	55 seconds
✔️	get-organization	2025-03-19 12:17:58+00:00	55 seconds
✔️	get-pyxis-certification-data	2025-03-19 12:18:53+00:00	49 seconds
✔️	copy-bundle-image-to-released-registry	2025-03-19 12:19:42+00:00	23 seconds
✔️	get-supported-versions	2025-03-19 12:20:05+00:00	43 seconds
✔️	add-bundle-to-fbc	2025-03-19 12:20:05+00:00	a minute
✔️	acquire-lease	2025-03-19 12:20:48+00:00	7 seconds
✔️	add-bundle-to-index	2025-03-19 12:20:55+00:00	16 minutes
✔️	sign-index-image	2025-03-19 12:36:56+00:00	39 seconds
✔️	publish-to-index	2025-03-19 12:37:35+00:00	10 minutes

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

Release info

Released bundle:

quay.io/community-operator-pipeline-prod/vault-config-operator:0.8.30

Updated indices:

registry.redhat.io/redhat/community-operator-index:v4.12
registry.redhat.io/redhat/community-operator-index:v4.13
registry.redhat.io/redhat/community-operator-index:v4.14
registry.redhat.io/redhat/community-operator-index:v4.15
registry.redhat.io/redhat/community-operator-index:v4.16
registry.redhat.io/redhat/community-operator-index:v4.17
registry.redhat.io/redhat/community-operator-index:v4.18

Troubleshooting

Please refer to the troubleshooting guide.

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

vault-config-operator release 0.8.30

f80e76c

Signed-off-by: raffaelespazzoli <[email protected]>

rh-operator-bundle-bot added the operator-hosted-pipeline/started label Mar 17, 2025

rh-operator-bundle-bot approved these changes Mar 17, 2025

View reviewed changes

rh-operator-bundle-bot changed the title ~~vault-config-operator new version 0.8.30~~ operator vault-config-operator (0.8.30) Mar 17, 2025

rh-operator-bundle-bot added operator-hosted-pipeline/failed and removed operator-hosted-pipeline/started labels Mar 17, 2025

tomasbakk added the pipeline/trigger-hosted label Mar 19, 2025

rh-operator-bundle-bot added operator-hosted-pipeline/started and removed pipeline/trigger-hosted operator-hosted-pipeline/failed labels Mar 19, 2025

rh-operator-bundle-bot approved these changes Mar 19, 2025

View reviewed changes

rh-operator-bundle-bot merged commit fad163f into redhat-openshift-ecosystem:main Mar 19, 2025
1 of 2 checks passed

rh-operator-bundle-bot added operator-release-pipeline/started operator-hosted-pipeline/passed and removed operator-hosted-pipeline/started labels Mar 19, 2025

rh-operator-bundle-bot added operator-release-pipeline/failed and removed operator-release-pipeline/started labels Mar 19, 2025

tomasbakk added the pipeline/trigger-release label Mar 19, 2025

rh-operator-bundle-bot added the operator-release-pipeline/started label Mar 19, 2025

rh-operator-bundle-bot added operator-release-pipeline/passed and removed pipeline/trigger-release operator-release-pipeline/failed operator-release-pipeline/started labels Mar 19, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

operator vault-config-operator (0.8.30) #6197

operator vault-config-operator (0.8.30) #6197

raffaelespazzoli commented Mar 17, 2025

rh-operator-bundle-bot commented Mar 17, 2025

rh-operator-bundle-bot commented Mar 17, 2025

rh-operator-bundle-bot commented Mar 17, 2025

raffaelespazzoli commented Mar 17, 2025

tomasbakk commented Mar 18, 2025 •

edited

Loading

raffaelespazzoli commented Mar 18, 2025

tomasbakk commented Mar 19, 2025

rh-operator-bundle-bot commented Mar 19, 2025

rh-operator-bundle-bot commented Mar 19, 2025

rh-operator-bundle-bot commented Mar 19, 2025

rh-operator-bundle-bot commented Mar 19, 2025

rh-operator-bundle-bot commented Mar 19, 2025

operator vault-config-operator (0.8.30) #6197

operator vault-config-operator (0.8.30) #6197

Conversation

raffaelespazzoli commented Mar 17, 2025

New Submissions

Updates to existing Operators

Your submission should not

Operator Description must contain (in order)

Operator Metadata should contain

rh-operator-bundle-bot commented Mar 17, 2025

Static test results

rh-operator-bundle-bot commented Mar 17, 2025

rh-operator-bundle-bot commented Mar 17, 2025

Pipeline Summary

Tasks

Troubleshooting

raffaelespazzoli commented Mar 17, 2025

tomasbakk commented Mar 18, 2025 • edited Loading

raffaelespazzoli commented Mar 18, 2025

tomasbakk commented Mar 19, 2025

rh-operator-bundle-bot commented Mar 19, 2025

Static test results

rh-operator-bundle-bot commented Mar 19, 2025

rh-operator-bundle-bot commented Mar 19, 2025

Pipeline Summary

Tasks

Troubleshooting

rh-operator-bundle-bot commented Mar 19, 2025

Pipeline Summary

Tasks

Troubleshooting

rh-operator-bundle-bot commented Mar 19, 2025

Pipeline Summary

Tasks

Release info

Troubleshooting

tomasbakk commented Mar 18, 2025 •

edited

Loading