operator forklift-operator (2.6.3-1)

[liranr23]

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

New Submissions

• [ ] Are you familiar with our contribution guidelines?
• [ ] Are you familiar with our operator pipeline?
• [ ] Have you tested your Operator with all Custom Resource Definitions packaging?
• [ ] 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?

Your submission should not

• [ ] Add more than one operator bundle per PR
• [ ] Modify any operator
• [ ] Rename an operator
• [ ] 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 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

• [ ] 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]

Static test results

Status	Check	Message
:x:	check_dangling_bundles	Channel stable-v2.6 has dangling bundles: {Bundle(forklift-operator/2.6.3-1)}
:warning:	check_osdk_bundle_validate_operator_framework	Warning: Value forklift-operator.v2.6.3-1: unable to find the resource requests for the container: (forklift-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline PipelineRun: operator-hosted-pipeline-runjz8zt Start Time: 2024-07-02 14:55:36+00:00

Tasks

Status	Task	Start Time	Duration
:heavy_check_mark:	get-pr-number	2024-07-02 14:55:38+00:00	7 seconds
:heavy_check_mark:	acquire-lease	2024-07-02 14:55:49+00:00	7 seconds
:heavy_check_mark:	set-github-started-label	2024-07-02 14:56:00+00:00	9 seconds
:heavy_check_mark:	set-github-status-pending	2024-07-02 14:56:11+00:00	8 seconds
:heavy_check_mark:	set-env	2024-07-02 14:56:23+00:00	8 seconds
:heavy_check_mark:	clone-repository-base	2024-07-02 14:56:33+00:00	29 seconds
:heavy_check_mark:	clone-repository	2024-07-02 14:56:34+00:00	33 seconds
:heavy_check_mark:	detect-changes	2024-07-02 14:57:11+00:00	a minute
:heavy_check_mark:	check-permissions	2024-07-02 14:58:30+00:00	a minute
:heavy_check_mark:	set-github-pr-title	2024-07-02 14:59:31+00:00	7 seconds
:heavy_check_mark:	read-config	2024-07-02 14:59:40+00:00	51 seconds
:heavy_check_mark:	apply-test-waivers	2024-07-02 15:00:35+00:00	50 seconds
:heavy_check_mark:	content-hash	2024-07-02 15:01:26+00:00	11 seconds
:heavy_check_mark:	certification-project-check	2024-07-02 15:01:40+00:00	45 seconds
:heavy_check_mark:	get-organization	2024-07-02 15:02:27+00:00	48 seconds
:heavy_check_mark:	get-pyxis-certification-data	2024-07-02 15:03:16+00:00	13 seconds
:heavy_check_mark:	static-tests	2024-07-02 15:03:31+00:00	51 seconds
:heavy_check_mark:	yaml-lint	2024-07-02 15:03:32+00:00	46 seconds
:heavy_check_mark:	merge-registry-credentials	2024-07-02 15:03:33+00:00	a minute
:x:	static-tests-results	2024-07-02 15:04:24+00:00	16 seconds

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

Troubleshooting

Please refer to the troubleshooting guide.

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