Update rebasebot alert configs for PIXAA organisation#79597
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
WalkthroughThe PR updates rebasebot CI job configuration to redistribute Slack notifications across teams and reassign ownership. Nine cloud provider and cluster-api jobs are rerouted to pixaa-alerts, six jobs have notifications disabled, and the kubernetes-autoscaler job transfers to autoscaling-team with updated credentials and bot identities. ChangesRebasebot notification and team configuration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
🚥 Pre-merge checks | ✅ 12✅ Passed checks (12 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
openshift-ci
Bot
added
the
approved
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo, JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse |
|
@JoelSpeed: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@JoelSpeed: The following tests 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. |
2 participants
As part of the pixaa reorg, I'm moving all alerts for the rebase bot related to PIXAA repos to a new #pixaa-rebasebot-alerts channel.
The old team cloud rebasebot channel will be archived.
There currently isn't a good place to redirect the IBM or nutanix webhooks to, I don't think PIXAA is intending to own these going forward.
I've also updated the kubernetes autoscaler to move to the autoscaling team
CC @damdo @RadekManak @elmiko
Summary by CodeRabbit
This pull request updates the rebasebot scheduled job alert configuration in OpenShift CI infrastructure to route Slack notifications based on organizational changes.
Changes Made
File Modified:
ci-operator/config/openshift-eng/rebasebot/openshift-eng-rebasebot-main.yamlThe PR reconfigures Slack webhook destinations for several rebasebot scheduled jobs that monitor upstream Kubernetes and cloud provider repositories:
Cloud Provider Jobs Migrated to PIXAA Channel: Updated the Slack webhook for the following rebasebot jobs to send alerts to the new PIXAA organization's dedicated channel:
cloud-provider-awscluster-api-provider-azurecluster-api-provider-awscluster-api-provider-gcpThese jobs previously sent alerts to
/secrets/rebasebot/team-cloud-slack-webhookand now use/secrets/rebasebot/pixaa-alerts-slack-webhook.Kubernetes Autoscaler Ownership Transferred: The
kubernetes-autoscalerjob was updated to use autoscaling-team specific credentials and alert routing:/secrets/rebasebot/autoscaling-team-bot-spam-slack-incoming-webhookImpact
This reorganization consolidates cloud infrastructure rebasebot alerts under the PIXAA organization's dedicated Slack channel while transferring the Kubernetes autoscaler monitoring responsibility to the autoscaling team, allowing each team to manage their relevant upstream rebase notifications independently.