Bump CVP FIPS cluster pool instances to m6a.2xlarge#82030
Conversation
FIPS jobs are hitting resource pressure on m6a.xlarge nodes; bump control plane and compute instance types to m6a.2xlarge for all CVP FIPS AWS install configs. Assisted-By: Claude Fable 5 Signed-off-by: Mat Kowalski <mko@redhat.com>
|
[REHEARSALNOTIFIER] Note: If this PR includes changes to step registry files ( |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (7)
WalkthroughChangesAWS FIPS instance sizing
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mkowalski The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@mkowalski: all tests passed! 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. |
|
Wrong approach — the affected FIPS jobs are IPI, not cluster-pool claims. Replacing with per-job env overrides. |
Bumps control plane and compute instance types from m6a.xlarge to m6a.2xlarge in all CVP FIPS AWS install configs, per capacity issues discussed in Slack thread.
Summary by CodeRabbit
m6a.2xlargeinstead ofm6a.xlarge.