Skip to content

ROSAENG-61679: Update .tekton pipelines for tenant migration to kflux-prd-rh03#591

Open
nephomaniac wants to merge 1 commit into
openshift:masterfrom
nephomaniac:ROSAENG-61679/tekton-tenant-migration
Open

ROSAENG-61679: Update .tekton pipelines for tenant migration to kflux-prd-rh03#591
nephomaniac wants to merge 1 commit into
openshift:masterfrom
nephomaniac:ROSAENG-61679/tekton-tenant-migration

Conversation

@nephomaniac

@nephomaniac nephomaniac commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Update 6 .tekton pipeline files: namespace from camo-hcm-tenant to configure-alertmanager-operator-tenant
  • Update output-image paths from camo-hcm-tenant/configure-alertmanager-operator-master/ to configure-alertmanager-operator-tenant/openshift/
  • Update application/component labels to match new Component CR names on kflux-prd-rh03

Dependencies

This PR is on hold until the Konflux tenant migration MR merges and ArgoCD syncs:

Once that MR merges, ArgoCD will create the configure-alertmanager-operator-tenant namespace with Application/Component CRs on kflux-prd-rh03. Only then can this PR be unblocked (/hold cancel) and merged.

Context

Part of ROSAENG-61679 — migrating CAMO's Konflux tenant from the non-standard camo-hcm-tenant on stone-prd-rh01 to configure-alertmanager-operator-tenant on kflux-prd-rh03, matching all other SRE operator tenants.

Jira: https://redhat.atlassian.net/browse/ROSAENG-61679

🤖 Generated with Claude Code

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 13, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 13, 2026

Copy link
Copy Markdown

@nephomaniac: This pull request references ROSAENG-61679 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • Update 6 .tekton pipeline files: namespace from camo-hcm-tenant to configure-alertmanager-operator-tenant
  • Update output-image paths from camo-hcm-tenant/configure-alertmanager-operator-master/ to configure-alertmanager-operator-tenant/openshift/
  • Update application/component labels to match new Component CR names on kflux-prd-rh03

Context

Depends on konflux-release-data MR that creates the new tenant on kflux-prd-rh03. Do NOT merge until that MR is merged and ArgoCD has synced.

Jira: https://redhat.atlassian.net/browse/ROSAENG-61679

🤖 Generated with Claude Code

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 openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nephomaniac, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: dc3486f3-d563-4961-9e1c-787db204fdd2

📥 Commits

Reviewing files that changed from the base of the PR and between a65bd31 and 99f489c.

📒 Files selected for processing (6)
  • .tekton/configure-alertmanager-operator-master-pull-request.yaml
  • .tekton/configure-alertmanager-operator-master-push.yaml
  • .tekton/configure-alertmanager-operator-pko-pull-request.yaml
  • .tekton/configure-alertmanager-operator-pko-push.yaml
  • .tekton/e2e-master-pull-request.yaml
  • .tekton/e2e-master-push.yaml

Walkthrough

Changes

Tekton pipeline wiring

Layer / File(s) Summary
Tenant and image destination migration
.tekton/configure-alertmanager-operator-*.yaml, .tekton/e2e-*.yaml
PipelineRun identities and namespaces now use configure-alertmanager-operator, while output images use the corresponding tenant repository paths and revision-based tags.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: red-hat-konflux[bot], jbpratt, tnierman, ritmun

🚥 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.
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 The PR only updates .tekton YAML manifests; no Ginkgo test titles are added or modified, so the stability check is not applicable.
Test Structure And Quality ✅ Passed PASS: The PR only changes six Tekton PipelineRun YAMLs; no Ginkgo tests or test setup/assertion code are modified, so this check is not applicable.
Microshift Test Compatibility ✅ Passed The PR only updates .tekton PipelineRun manifests; no Ginkgo e2e test code or new test cases were added, so MicroShift test compatibility isn’t implicated.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR only updates Tekton PipelineRun YAMLs; no new Ginkgo/e2e test code or SNO-sensitive test logic was added.
Topology-Aware Scheduling Compatibility ✅ Passed The PR only changes Tekton PipelineRun metadata, namespaces, image paths, and service accounts; no affinity, nodeSelector, spread, replica, or PDB scheduling constraints were added.
Ote Binary Stdout Contract ✅ Passed PR only updates .tekton PipelineRun YAML; no process-level Go/test setup code changed, so the OTE stdout contract is unaffected.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PASS: The PR only changes Tekton PipelineRun YAML; no Ginkgo tests or new IPv4/external-network assumptions were added.
No-Weak-Crypto ✅ Passed Only Tekton YAML metadata/image-path changes; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret-comparison code appears in the diff.
Container-Privileges ✅ Passed The six changed Tekton PipelineRun manifests contain no privileged, hostPID/network/IPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The modified .tekton manifests only rename tenant/image/labels and reference a git auth secret; no logging, echo, or sensitive values were added.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: updating .tekton pipelines for a tenant migration to kflux-prd-rh03.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci Bot requested review from theautoroboto and zmird-r July 13, 2026 20:21
@openshift-ci

openshift-ci Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nephomaniac

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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 13, 2026
@nephomaniac

Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 13, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.tekton/configure-alertmanager-operator-master-pull-request.yaml:
- Around line 14-26: Update the serviceAccountName values to match the renamed
Konflux components: in
.tekton/configure-alertmanager-operator-master-pull-request.yaml lines 14-26 and
.tekton/configure-alertmanager-operator-master-push.yaml lines 13-25, use
build-pipeline-configure-alertmanager-operator; in
.tekton/e2e-master-pull-request.yaml lines 14-26 and
.tekton/e2e-master-push.yaml lines 13-25, use
build-pipeline-configure-alertmanager-operator-e2e.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 46f841b1-ea3e-4031-8568-28caf7d0ad54

📥 Commits

Reviewing files that changed from the base of the PR and between 95b8d9a and a65bd31.

📒 Files selected for processing (6)
  • .tekton/configure-alertmanager-operator-master-pull-request.yaml
  • .tekton/configure-alertmanager-operator-master-push.yaml
  • .tekton/configure-alertmanager-operator-pko-pull-request.yaml
  • .tekton/configure-alertmanager-operator-pko-push.yaml
  • .tekton/e2e-master-pull-request.yaml
  • .tekton/e2e-master-push.yaml

Comment thread .tekton/configure-alertmanager-operator-master-pull-request.yaml
@codecov

codecov Bot commented Jul 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.61%. Comparing base (95b8d9a) to head (a65bd31).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #591   +/-   ##
=======================================
  Coverage   67.61%   67.61%           
=======================================
  Files           8        8           
  Lines        1124     1124           
=======================================
  Hits          760      760           
  Misses        330      330           
  Partials       34       34           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

…-prd-rh03

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@nephomaniac nephomaniac force-pushed the ROSAENG-61679/tekton-tenant-migration branch from 170eb2a to 99f489c Compare July 13, 2026 22:03
@openshift-ci

openshift-ci Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

@nephomaniac: 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.

@nephomaniac

Copy link
Copy Markdown
Contributor Author

The konflux jobs/checks will likely fail until this PR creating the missing namespace, etc. is merged:
https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/20277

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants