Skip to content

docs: proposal to replace CodePipeline with CloudFormation stacks - #689

Draft
jmelis wants to merge 1 commit into
mainfrom
docs/codepipeline-removal
Draft

docs: proposal to replace CodePipeline with CloudFormation stacks#689
jmelis wants to merge 1 commit into
mainfrom
docs/codepipeline-removal

Conversation

@jmelis

@jmelis jmelis commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Proposal to remove the three-tier AWS CodePipeline architecture and replace it with CloudFormation stacks for RC/MC cluster lifecycle management
  • Internal repo (rosa-hyperfleet-internal) expands to own all account-level infrastructure across all environments
  • New MC Autoscaler component manages MC capacity in stable environments
  • Developer flow analysis: faster provisioning, separated infra/app resync, single-phase teardown

Open questions for the team

  1. CloudFormation vs. keeping Terraform (with Terraform Cloud as orchestrator)
  2. MC Autoscaler design (capacity signals, scale-down policy)
  3. CloudFormation template testing strategy
  4. CI integration details for ephemeral environments

🤖 Generated with Claude Code

Covers the three pillars: internal repo owns all account infra,
CloudFormation stacks for RC/MC provisioning, and MC Autoscaler
for stable environments. Includes developer flow analysis and
migration strategy.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@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 Jul 17, 2026
@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign psav for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 94b32c73-115b-4a25-a9c0-234a380ceac2

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
  • Commit unit tests in branch docs/codepipeline-removal

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

@typeid

typeid commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

/jira-refresh


| Option | How It Works | Pros | Cons |
| --- | --- | --- | --- |
| **Terraform Cloud** | Workspaces per cluster, VCS-triggered or API-driven runs | Managed state, plan/apply UI, team workflows, native GitHub integration | Cost per workspace, external dependency, network access to private resources |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is fedRAMP being considered here?

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

Labels

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.

3 participants