-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate ephemeral MCs for MC app testing #3718
Comments
So I don't forget, the new ephemeral MCs should go into AWS account |
For the name of the MCs we decided to use |
An update on where things are at as I plan to park this issue until I'm back from KubeCon / KCD Denmark:
Full details of the issue experienced can be found in this Slack Thread but to summarise: The new AWS that we are using for these ephemeral MCs doesn't have the root hosted zone setup in Route53 (as this is already setup in the other account that |
After discussing in Phoenix stand up the problem with |
@JosephSalisbury 👆 FYI as it effects the MC moves we're wanting to do and might need to be included in some of your issues about account separation. Any suggestions for what we should use for the new base domain? @fiunchinho do you know if we have docs anywhere on how we set up a new hosted zone for giant swarm addresses? Or should I maybe speak with an SRE? |
I added this, I hope that helps https://github.com/giantswarm/mc-bootstrap/pull/1062 |
🫶 You spoil me! Thats great! Thank you! |
Desired outcome is that we know how an ephemeral MC looks like and how to create one.
Acceptance criteria:
The text was updated successfully, but these errors were encountered: