ci: add missing FBC catalog for console-plugin-operator-fbc-4-22 - #83
Open
anandkuma77 wants to merge 1 commit into
Open
ci: add missing FBC catalog for console-plugin-operator-fbc-4-22#83anandkuma77 wants to merge 1 commit into
anandkuma77 wants to merge 1 commit into
Conversation
The console-plugin-operator-fbc-4-22-on-pull-request/on-push Konflux
pipelines expect a File-Based Catalog Containerfile at
catalog/v4.22/Containerfile, but the catalog/ directory was never
added, so every run fails with "Cannot find Dockerfile
catalog/v4.22/Containerfile".
Add the FBC structure, mirroring the pattern used by
openshift/cert-manager-operator-release (catalog/v4.22/Containerfile +
catalog/v4.22/catalog/<package>/{package,channel,bundle-*}.yaml),
populated from this repo's existing operator bundle metadata
(package: ocp-secrets-management-operator, channel: alpha, v0.1.0).
Image references use the registry.stage.redhat.io prefix required by
Enterprise Contract's olm.allowed_registries_related check.
Validated locally with `opm validate` and `opm serve --cache-only`
using the quay.io/operator-framework/opm image.
Co-authored-by: Cursor <cursoragent@cursor.com>
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
anandkuma77
marked this pull request as ready for review
July 3, 2026 10:44
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
@anandkuma77: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The console-plugin-operator-fbc-4-22-on-pull-request/on-push Konflux pipelines expect a File-Based Catalog Containerfile at catalog/v4.22/Containerfile, but the catalog/ directory was never added, so every run fails with "Cannot find Dockerfile catalog/v4.22/Containerfile".
Add the FBC structure, mirroring the pattern used by openshift/cert-manager-operator-release (catalog/v4.22/Containerfile + catalog/v4.22/catalog//{package,channel,bundle-*}.yaml), populated from this repo's existing operator bundle metadata (package: ocp-secrets-management-operator, channel: alpha, v0.1.0). Image references use the registry.stage.redhat.io prefix required by Enterprise Contract's olm.allowed_registries_related check.
Validated locally with
opm validateandopm serve --cache-onlyusing the quay.io/operator-framework/opm image.