Change google project for preview DNS's #10385
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: ArthurSens <arthursens2005@gmail.com>
ArthurSens
force-pushed
the
as/migrate-preview-dns
branch
from
c430850 to
0de0390
Compare
meysholdt
approved these changes
Jun 4, 2022
Signed-off-by: ArthurSens <arthursens2005@gmail.com>
|
We cannot forget to clean up |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
gitpod-devis one of our oldest google projects that was used to manage all kinds of cloud resources in the past.We're working towards more fine-grained billing cost allocations and one of the changes is that DNS records from preview environments will now be handled in the
gitpod-core-devproject.This particular PR does only one of the many steps necessary for the DNS migration and should be merged only when @meysholdt and I perform the migration. (Probably next Saturday 4/06)
Related Issue(s)
One of the steps for https://github.com/gitpod-io/ops/issues/2533
How to test
When performing the migration, a werft job should be run from this PR to make sure it is configured correctly. Make sure to use core-dev during the test, and not our default harvester previews
Release Notes