You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current AWS account used for the nightly RKE2 and EKS CI should not be used anymore. Instead we should move to a new account provisioned through the new account management (Spacelift).
Note that there are a few resources in the current account that we will need to create in a new account (primarily state related items like a state bucket and dynamodb table, as well as any OIDC conntections to enable AWS access from uds-core CI).
Definition of done:
New account created using the new provisioning process (named/scoped specifically to uds-core-ci)
Account access provided for UDS Core developers to debug/look into CI issues
Any AWS resources necessary for IAC CI created in the new account (bucket, dynamodb, iam, etc)
Secrets/variables updated in uds-core to use the new account
All IAC CI passing (EKS/RKE2 are the two that run in AWS)
AWS "nuke"/cleanup would be nice to have but can be completed as follow ons unless easy to setup throughout the process. The old account SHOULD NOT be deleted yet as other repositories/teams may be leveraging this account still.
The text was updated successfully, but these errors were encountered:
Happy to help with this. Here are some broken down high level steps I would recommend:
Create a directory in the uds-core repo that will hold the static infra for the CI AWS account. You could probably steal code from here
Create an AWS Account by adding a config here that links the directory created in 1 to this AWS account
Update secrets in uds-core to point to the new OIDC roles, state buckets, and lock table created in 1
We don't have a nuke workflow setup, but I am thinking we could create a workflow in spacelift to run nuke for specific accounts. Created an issue for that here. Should be a relatively easy lift to implement.
The current AWS account used for the nightly RKE2 and EKS CI should not be used anymore. Instead we should move to a new account provisioned through the new account management (Spacelift).
Note that there are a few resources in the current account that we will need to create in a new account (primarily state related items like a state bucket and dynamodb table, as well as any OIDC conntections to enable AWS access from uds-core CI).
Definition of done:
AWS "nuke"/cleanup would be nice to have but can be completed as follow ons unless easy to setup throughout the process. The old account SHOULD NOT be deleted yet as other repositories/teams may be leveraging this account still.
The text was updated successfully, but these errors were encountered: