Skip to content

[WIP] Added 250 throughput for masters aws ec2 volumes#5047

Open
hector-vido wants to merge 1 commit intoopenshift:mainfrom
hector-vido:cluster-init-aws-throughput
Open

[WIP] Added 250 throughput for masters aws ec2 volumes#5047
hector-vido wants to merge 1 commit intoopenshift:mainfrom
hector-vido:cluster-init-aws-throughput

Conversation

@hector-vido
Copy link
Contributor

@openshift-ci-robot
Copy link
Contributor

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: automatic mode

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 25, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 25, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Excluded labels (none allowed) (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f35bb0a3-e59e-4301-94b6-1ed808d99431

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@hector-vido hector-vido force-pushed the cluster-init-aws-throughput branch from 4c096c2 to f596d46 Compare March 25, 2026 15:03
@openshift-ci openshift-ci bot requested review from deepsm007 and psalajova March 25, 2026 15:04
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hector-vido

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 Mar 25, 2026
@hector-vido hector-vido force-pushed the cluster-init-aws-throughput branch 3 times, most recently from 5c7c8f1 to 17cd7fd Compare March 26, 2026 03:44
@hector-vido hector-vido force-pushed the cluster-init-aws-throughput branch from 17cd7fd to 53670c0 Compare March 26, 2026 03:48
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 26, 2026

@hector-vido: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/breaking-changes 53670c0 link false /test breaking-changes
ci/prow/checkconfig 53670c0 link true /test checkconfig
ci/prow/integration 53670c0 link true /test integration

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.

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/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants