Prepare bgp-cloud-connector for GA: stable channel, 1.0 CPE

[alebedev87]

Summary

Prepares the operator's OLM delivery metadata for the upcoming GA release, while keeping the operator itself at 0.0.1 and retaining the preview status for now.

Changes:

• OLM channel — add a stable channel as the new default and flip the bundle metadata (Makefile defaults, bundle.Dockerfile, Containerfile.bgp-cloud-connector-bundle, bundle/metadata/annotations.yaml) to stable.
• FBC — in catalog/v4.22/catalog-template.yaml and catalog/v4.22/catalog.yaml, add the stable channel (containing the current 0.0.1 bundle) and set it as defaultChannel. The existing alpha channel is kept for the moment so the already-published preview bundles are not pruned; it can be pruned in a later release.
• CPE label 0.1 → 1.0 — in Containerfile.bgp-cloud-connector and Containerfile.bgp-cloud-connector-bundle, matching the new 1.0 content stream registered in pyxis-repo-configs / konflux-release-data.

Not changed (intentionally)

• Operator version stays 0.0.1 — we keep shipping the 0.0.1 image under the new 1.0 content stream until we decide to cut 1.0.z.
• CSV maturity stays alpha.
• The preview/internal-testing disclaimer in the CSV description is retained.
• v1alpha1 API versions and fips-compliant: "false" are unchanged.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [alebedev87]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 2659fb11-bb59-4b88-b7ab-c622f024b11d

📥 Commits

Reviewing files that changed from the base of the PR and between 31c4175 and 48332d9.

📒 Files selected for processing (3)

• Makefile
• catalog/v4.22/catalog-template.yaml
• catalog/v4.22/catalog.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

The change promotes the bundle’s default and available channel from alpha to stable across container labels, bundle metadata, and OLM catalogs. The catalogs retain the alpha channel and add a stable entry for version v0.0.1. Image CPE labels change from version 0.1 to 1.0. The Makefile adds configurable bundle namespace, run flags, cleanup flags, and targets for deploying or removing the bundle-based operator.

Suggested reviewers: omark-rh

Merge Risk: ⚪ Minimal · up to 48332

This PR updates release-channel and CPE metadata without supplied evidence of a concrete correctness, security, availability, or deployment risk; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PASS — the pull request commit changes only two Containerfiles, the Makefile, bundle metadata, and catalog YAML. git diff HEAD^ HEAD shows no test files and no additions or modifications to It, `D…
Test Structure And Quality	✅ Passed	PASS: The pull request changes only two Containerfiles, the Makefile, bundle metadata, and catalog YAML. The exact HEAD commit contains no Ginkgo test files, Go source files, or test-like paths. There…
Microshift Test Compatibility	✅ Passed	PASS — The pull request changes only seven container, Makefile, bundle metadata, and catalog files. The exact diff contains no added or modified test files, and no new Ginkgo declarations. The MicroSh…
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The pull request adds no Ginkgo tests and changes no test paths. The exact patch only updates container labels, Makefile channel defaults, bundle metadata, and catalog entries. Therefore, the SN…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS — The pull request does not add or modify deployment manifests, operator code, or controllers. The verified diff changes only container labels, OLM channel metadata, Makefile channel defaults, an…
Ote Binary Stdout Contract	✅ Passed	PASS — the pull request changes only Containerfiles, Makefile channel defaults, and catalog/metadata YAML. git diff HEAD^ HEAD shows no Go source or test-file changes, and no process-level stdout wr…
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS: The pull-request patch changes only container labels, Makefile channel defaults, bundle metadata, and catalog YAML. git diff --name-status HEAD^ HEAD lists no test files, and the added lines c…
No-Weak-Crypto	✅ Passed	PASS: The PR changes only channel metadata, CPE labels, Makefile channel defaults, and catalog entries. The exact diff adds no MD5, SHA1, DES, 3DES, RC4, Blowfish, ECB, custom crypto, or secret/token …
Container-Privileges	✅ Passed	PASS. The pull-request diff changes only CPE labels, OLM channel metadata, and catalog entries. It adds no privileged: true, host namespace settings, SYS_ADMIN, root runtime, or `allowPrivilegeEsc…
No-Sensitive-Data-In-Logs	✅ Passed	PASS — The pull request changes only image CPE labels, OLM channel metadata, and catalog entries. The committed diff adds no logging calls, command output of sensitive variables, or sensitive data. Th…
Title check	✅ Passed	The title clearly summarizes the primary changes: preparing the operator for GA by switching to the stable channel and updating the CPE label to 1.0.
Description check	✅ Passed	The description directly explains the channel, CPE label, catalog, version, and intentionally unchanged metadata changes in the pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

Full details: Stable And Deterministic Test Names

Explanation

PASS — the pull request commit changes only two Containerfiles, the Makefile, bundle metadata, and catalog YAML. git diff HEAD^ HEAD shows no test files and no additions or modifications to It, Describe, Context, or When titles. Therefore, the pull request introduces no dynamic or overly-specific Ginkgo test name.

Full details: Test Structure And Quality

Explanation

PASS: The pull request changes only two Containerfiles, the Makefile, bundle metadata, and catalog YAML. The exact HEAD commit contains no Ginkgo test files, Go source files, or test-like paths. Therefore, it introduces no test-structure, cleanup, timeout, assertion-message, or test-pattern failure under this check.

Full details: Microshift Test Compatibility

Explanation

PASS — The pull request changes only seven container, Makefile, bundle metadata, and catalog files. The exact diff contains no added or modified test files, and no new Ginkgo declarations. The MicroShift compatibility check is therefore not applicable.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

PASS: The pull request adds no Ginkgo tests and changes no test paths. The exact patch only updates container labels, Makefile channel defaults, bundle metadata, and catalog entries. Therefore, the SNO multi-node test check is not applicable.

Full details: Topology-Aware Scheduling Compatibility

Explanation

PASS — The pull request does not add or modify deployment manifests, operator code, or controllers. The verified diff changes only container labels, OLM channel metadata, Makefile channel defaults, and catalog entries. It introduces no anti-affinity, topology spread, node selectors or affinity, tolerations, replica logic, or PDB settings. Existing scheduling fields in the CSV and CR manifests are outside the pull-request diff, so this check has no introduced topology-compatibility failure.

Full details: Ote Binary Stdout Contract

Explanation

PASS — the pull request changes only Containerfiles, Makefile channel defaults, and catalog/metadata YAML. git diff HEAD^ HEAD shows no Go source or test-file changes, and no process-level stdout write was introduced. Existing cmd/main.go logging and Ginkgo suite setup are unchanged, so they cannot cause a pull-request-causal failure under this check.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS: The pull-request patch changes only container labels, Makefile channel defaults, bundle metadata, and catalog YAML. git diff --name-status HEAD^ HEAD lists no test files, and the added lines contain no Ginkgo declarations or network operations. Existing e2e tests are unchanged, so this check has no applicable new test.

Full details: No-Weak-Crypto

Explanation

PASS: The PR changes only channel metadata, CPE labels, Makefile channel defaults, and catalog entries. The exact diff adds no MD5, SHA1, DES, 3DES, RC4, Blowfish, ECB, custom crypto, or secret/token comparison logic. Repository-wide weak-crypto matches are confined to pre-existing vendored dependencies and are not changed by this commit.

Full details: Container-Privileges

Explanation

PASS. The pull-request diff changes only CPE labels, OLM channel metadata, and catalog entries. It adds no privileged: true, host namespace settings, SYS_ADMIN, root runtime, or allowPrivilegeEscalation: true. The operator image still uses USER 65532:65532, and the source and bundled deployment use runAsNonRoot: true, allowPrivilegeEscalation: false, and drop all capabilities.

Full details: No-Sensitive-Data-In-Logs

Explanation

PASS — The pull request changes only image CPE labels, OLM channel metadata, and catalog entries. The committed diff adds no logging calls, command output of sensitive variables, or sensitive data. The Makefile target additions described in the summary are not part of this commit; the actual diff changes only CHANNELS and DEFAULT_CHANNEL from alpha to stable. No explicit sensitive-data-in-logs condition is introduced.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[alebedev87]

/hold

Until https://gitlab.cee.redhat.com/releng/pyxis-repo-configs/-/merge_requests/1525 and https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/22125 merged.

[alebedev87]

/retest

[alebedev87]

/unhold

[openshift-ci]

@alebedev87: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.