Skip to content

Conversation

@kubasikus
Copy link
Contributor

Now that the exporter has been tested in stage, move forward with deploying the registry monitoring exporter to all stage and production member clusters.

@openshift-ci openshift-ci bot requested review from avi-biton and elsony December 10, 2025 09:25
@github-actions
Copy link
Contributor

🤖 Gemini AI Assistant Available

Hi @kubasikus! I'm here to help with your pull request. You can interact with me using the following commands:

Available Commands

  • @gemini-cli /review - Request a comprehensive code review

    • Example: @gemini-cli /review Please focus on security and performance
  • @gemini-cli <your question> - Ask me anything about the codebase

    • Example: @gemini-cli How can I improve this function?
    • Example: @gemini-cli What are the best practices for error handling here?

How to Use

  1. Simply type one of the commands above in a comment on this PR
  2. I'll analyze your code and provide detailed feedback
  3. You can track my progress in the workflow logs

Permissions

Only OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage.


This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance.

@github-actions
Copy link
Contributor

🤖 Hi @kubasikus, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

@kubasikus kubasikus changed the title Deploy to prod PVO11Y-5019 Deploy container registry monitoring to prod Dec 10, 2025
@mftb
Copy link
Contributor

mftb commented Dec 10, 2025

@hugares @filariow can we have an infra review on this?

Copy link
Contributor

@pacho-rh pacho-rh left a comment

Choose a reason for hiding this comment

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

/lgtm

@TominoFTW
Copy link
Contributor

/retest

…ll member clusters

Move away from having cluster-specific deployment folders. This is not necessary, as the exporter configuration is expected to be the same across all clusters.
This aligns with the intent to deploy this monitoring exporter to all member clusters.
Use the overlay patch to set the target environment of our ApplicationSet. Also cleanup the deletion fix we previously put in place to prevent production deployment.
This path no longer exists.
@openshift-ci
Copy link

openshift-ci bot commented Dec 10, 2025

New changes are detected. LGTM label has been removed.

@raks-tt raks-tt added the lgtm label Dec 10, 2025
@openshift-ci
Copy link

openshift-ci bot commented Dec 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kubasikus, pacho-rh, raks-tt, TominoFTW

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 [kubasikus,pacho-rh,raks-tt]

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

@openshift-merge-bot openshift-merge-bot bot merged commit 96ced92 into main Dec 10, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants