Skip to content

Cost saving: Move "cedric" env to us-east1#533

Merged
jochenehret merged 1 commit into
mainfrom
move_cedric_useast1
Jun 30, 2025
Merged

Cost saving: Move "cedric" env to us-east1#533
jochenehret merged 1 commit into
mainfrom
move_cedric_useast1

Conversation

@jochenehret

Copy link
Copy Markdown
Contributor

No description provided.

@jochenehret jochenehret requested review from a team June 30, 2025 12:23

@oliver-heinrich oliver-heinrich left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM - just one question: are the resources already created in the former region 'europe-west3' also deleted when the bbl env is recreated and deployed in the region 'us-east1' or where is this done?

@jochenehret

jochenehret commented Jun 30, 2025

Copy link
Copy Markdown
Contributor Author

The procedure is as follows:

  1. Pause the "cf-deployment" pipeline
  2. Destroy the existing bbl env in the old region with the "destroy-infrastructure" job
  3. Update the "infrastructure" pipeline
  4. Recreate the bbl env in the new region with the "setup-infrastructure" job
  5. Update DNS entries (not sure if this needs to be done manually)
  6. Unpause the "cf-deployment" pipeline.

I would test this approach with one bbl env first.

@jochenehret

Copy link
Copy Markdown
Contributor Author

The "cedric" env has been moved to us-east1. Pipeline has been updated. Procedure works as described above.

@jochenehret jochenehret merged commit 4d0c30a into main Jun 30, 2025
11 checks passed
@jochenehret jochenehret deleted the move_cedric_useast1 branch June 30, 2025 13:54
@jochenehret

Copy link
Copy Markdown
Contributor Author

ARD WG cost saving: cloudfoundry/community#1186

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants