Tracking 73 Kubernetes AWS Account Migrations from CNCF #4626

hh · 2023-01-13T11:09:21Z

There are 73 total Kubernetes accounts in the CNCF AWS Account. We will need to track these migrations.

arn:aws:servicequotas:::organizations/L-29A0C5DF is a request to raise the default max accounts from 10 to 200.

The process for moving accounts between organisations is outlined here: https://aws.amazon.com/premiumsupport/knowledge-center/organizations-move-accounts/

Kubernetes OU (3)

sig-infra-aws-admins+accounts@kubernetes.io (previously: k8s-infra-accounts@kubernetes.io)
sig-release-leads@kubernetes.io (password shared with @ cpanato)
k8s-infra-aws-root-account@kubernetes.io (password known by @ameukam and @dims)
registry.k8s.io OU (1)

registry.k8s.io OU (1)

k8s-infra-aws-admins+registry-k8s-io@kubernetes.io (previously k8s-infra-aws-registry-k8s-io-admin@kubernetes.io)

aws-ebs-csi-driver OU (1)

aws-ebs-csi-driver@lists.cncf.io

kops OU (4)

sig-k8s-infra OU (12)

capa OU (52)

hh · 2023-01-16T22:02:12Z

When planning our migration, we need to consider the following:

You have a valid payment method on the member account to address any charges that are incurred while the accounts are migrating.
I've opened Case ID: 11777279581 with AWS to research, but I'm trying to avoid doing this by hand. Suggestions and workarounds welcome here.
Before migrating, consider the number of accounts in your organization. If an increase is needed, see Quotas for AWS Organizations for more information.
I've submitted this, waiting on resolution. No update to arn:aws:servicequotas:::organizations/L-29A0C5DF yet.
You backed up any reports from the member accounts that you need to keep. The member accounts can't access these reports after leaving the Organization.
@dims @ameukam Let me know of any to migrate here.

hh · 2023-01-16T22:34:23Z

From https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_remove.html#orgs_manage_accounts_remove-from-master

Effects of removing an account from an organization

When you remove an account from an organization, no direct changes are made to the account. However, the following indirect effects occur:

The account is now responsible for paying its own charges and must have a valid payment method attached to the account.
I'm working on this now, trying to find some automation.
Integration with other services might be disabled. If you remove an account from an organization that has integration with an AWS service enabled, the users in that account can no longer use that service.
I'm not aware of any, but there just wanted this highlighted.

hh · 2023-01-17T02:20:47Z

It looks like we will need to detach each of the 73 accounts from the CNCF org, and at the moment I disconnect them we will need to provide credit card details (which can only be done via the Web Console / UI).

While I can do that, an account can only be part of a single org. So once detached, each of the accounts will need to be authenticated to to accept the invitation to join the new Kubernetes org.

It's unclear to me the best way to handle authenticating to these accounts as the passwords are likely handled in a distributed way by the Kubernetes community.

hh · 2023-01-17T02:30:59Z

I'm looking at options for authenticating to and accepting the handshake to join the new org once they are detached from the CNCF org.

We must authenticate as each account, and AssumeRole doesn't look like it will work once the accounts are standalone. Also the current passwords are unknown to the CNCF at an administrative level.

We'll need to decide on a process. We could reset the password on each account as we go and share each of them with #sig-k8s-infra, but I'm open to options.

I've thought about trying it for one of the top level accounts that is less used, like k8s-infra-accounts@kubernetes.io to test the process, but wanted to get buy-in for the reset password approach OR possibly escalating a ticket with Premium Support with AWS.

/cc @dims @ameukam

dims · 2023-01-17T03:23:47Z

@hh will let @ameukam reply on the "try with top level account". If we can escalate a ticket, we should just start that without delay.

hh · 2023-01-17T04:03:00Z

@dims can you help to escalate this Case ID : 11777279581 ?

Our official support plan is Basic, so I'm not sure I can do much on my end:
https://support.console.aws.amazon.com/support/home?region=us-west-2#/case/?displayId=11777279581&language=en

I'd also like to ensure that this service quota request to increase the default number of accounts was lifted from 10 to 200. We'll hit a roadblock pretty quick otherwise. It says Status: "CASE_CLOSED" but it's unclear if the quota was actually lifted. It's within this ticket, but I still can't verify. It was discussed in the body of this Case ID as well.

 aws service-quotas list-requested-service-quota-change-history                                                     
{
    "RequestedQuotas": [
        {
            "Id": "99e343d85b6c4879bf57682d792e24ddKWJ1tFl9",
            "CaseId": "11753963261",
            "ServiceCode": "organizations",
            "ServiceName": "AWS Organizations",
            "QuotaCode": "L-29A0C5DF",
            "QuotaName": "Default maximum number of accounts",
            "DesiredValue": 200.0,
            "Status": "CASE_CLOSED",
            "Created": "2023-01-13T23:58:00.061000+13:00",
            "LastUpdated": "2023-01-14T20:39:57.106000+13:00",
            "Requester": "{\"accountId\":\"348685125169\",\"callerArn\":\"arn:aws:iam::348685125169:root\"}",
            "QuotaArn": "arn:aws:servicequotas::348685125169:organizations/L-29A0C5DF",
            "GlobalQuota": true,
            "Unit": "None"
        }
    ]
}

hh · 2023-01-17T04:20:04Z

I'll work with @jeefy and @taylorwaggoner to get billing/card details to use during the migration. Once I have those we can try to move k8s-infra-accounts@kubernetes.io manually.

Steps:

Reset passwords for each account we migrate, or at least ensure Kubernetes access to the account without the CNCF Org (@hh / @ameukam)
- We will need to authenticate directly without CNCF or Kubernetes Org access.
- We should probably reset them all?
CNCF Provides credit card details in order to make account standalone (@hh) aws organizations remove-account-from-organization --account-id or via the Console (ALTERNATIVES TO THIS WELCOME!!)
Kubernetes Org admin issues (@hh / @ameukam) aws organizations invite-account-to-organization capturing the handshake id
Migrating Account authenticates via password or console to (@ameukam) aws organizations accept-handshake

upodroid · 2023-01-17T23:55:59Z

It is worth finding out if we need to retain most of these accounts. Are these accounts actually holding live infra or is it part of CI/CD usage like boskos projects? If they are part of a CI process and we can supply new accounts, we can provision fresh ones, reconfigure IAM, and use that opportunity to start on a clean slate.

hh · 2023-01-18T05:46:49Z

It is worth finding out if we need to retain most of these accounts.
@upodroid I agree

Are these accounts actually holding live infra or is it part of CI/CD usage like boskos projects?
Is there anyone who could identify these easily given the list? I have some automation ready to go through them, but we need a plan, it's a lot of accounts.

are they part of a CI process?
This migration is an ideal time to identify and consolidate.

I would suggest we add someone (or a role) from sig-k8s-infra to each of these accounts / mailing lists, so password resets can occur.

The Kubernetes OU is limited to accounts that contain k8s in the email:

aws organizations list-accounts --query 'sort_by(Accounts,&Email)[?contains(Email,k8s)==true].[Email]' | grep \" | wc -l

73

All but four of these are email lists maintained by kubernetes.io (google workspace groups / email lists?):
aws organizations list-accounts --query 'sort_by(Accounts,&Email)[?contains(Email,k8s)==true`].[Email]' | grep " | grep -v kubernetes.io;

        "cncf-k8s-external-dns-aws@lists.cncf.io"
        "cncf-k8s-infra-aws-capa-ami@lists.cncf.io"
        "cncf-k8s-infra-aws-capa-demo@lists.cncf.io"
        "cncf-k8s-minikube-aws@lists.cncf.io"

upodroid · 2023-01-18T11:29:47Z

Getting access to the *@kubernetes.io emails is easy.

Add your email to the groups in this file. Ignore everything between the + and @ symbols to get the email.

https://github.com/kubernetes/k8s.io/blob/main/groups/sig-k8s-infra/groups.yaml#L270

hh · 2023-01-18T18:31:56Z

Here are the emails associated with kubernetes.io:

aws organizations list-accounts --query 'sort_by(Accounts,&Email)[?contains(Email,`kubernetes.io`)==`true`].[Email]' | grep \"  | sed 's/+.*@/@/' | sort -u
        "k8s-infra-accounts@kubernetes.io"
        "k8s-infra-aws-admins@kubernetes.io"
        "k8s-infra-aws-registry-k8s-io-admin@kubernetes.io"
        "k8s-infra-aws-root-account@kubernetes.io"
        "sig-release-leads@kubernetes.io"

I'll put in a PR to add cncf-aws-admins@lists.cncf.io to each of these @upodroid.

Part of kubernetes#4626 (comment)

This list is associated with an AWS account that is part of a the migration to a new Kubernetes AWS Org in kubernetes#4626 This is to enable a password reset for that account and ensure someone within #sig-k8s-infra has password access to all Kubernetes AWS Org member accounts.

hh · 2023-01-18T18:47:18Z

Created #4645 for:

Created #4646 for:

sig-release-leads@kubernetes.io

I couldn't find these two lists in sig-k8s-infra/groups.yaml:

I'll use stsAssumeRole to see if there in any infrastructure contained within those last two. We will need to decide on a place to store the changed passwords (and ideally an AWS account password rotation policy).

ameukam · 2023-01-18T19:09:17Z

We need to move the AWS accounts under those emails:

we can revisit migration of the accounts used by Kops and CAPA.

ameukam · 2023-01-18T19:10:55Z

It is worth finding out if we need to retain most of these accounts. Are these accounts actually holding live infra or is it part of CI/CD usage like boskos projects? If they are part of a CI process and we can supply new accounts, we can provision fresh ones, reconfigure IAM, and use that opportunity to start on a clean slate.

I'm in favor of this approach. we can have a mix of accounts created and accounts migrated.

hh · 2023-01-18T19:26:02Z

Regarding account limit quota increase request, there was an update:

Service: AWS Organizations
Region: US East (Northern Virginia)
Limit name: Default maximum number of accounts
New limit value: 200

For a quota increase of this type, I will need to collaborate with our service team to get approval.

The team can take anything between 24-48 hours to provide feedback to the request, this is to ensure that we can meet your needs while keeping existing infrastructure safe.

I have marked the request as a priority in order to get feedback as soon as possible.

ameukam · 2023-01-18T20:49:52Z

@hh Sent an invite for k8s-infra-root-acocunt@kubernetes.io account. Can you talk a look in the org handshakes in the CNCF org:

$ aws organizations invite-account-to-organization --target Id=REDACTED,Type=ACCOUNT
{
    "Handshake": {
        "Id": "h-8201bc74bc5846f480ea2e63bed0b7dc",
        "Arn": "arn:aws:organizations::REDACTED:handshake/o-kz4vlkihvy/invite/h-8201bc74bc5846f480ea2e63bed0b7dc",
        "Parties": [
            {
                "Id": "kz4vlkihvy",
                "Type": "ORGANIZATION"
            },
            {
                "Id": "REDACTED",
                "Type": "ACCOUNT"
            }
        ],
        "State": "OPEN",
        "RequestedTimestamp": "2023-01-18T20:43:46.778000+00:00",
        "ExpirationTimestamp": "2023-02-02T20:43:46.778000+00:00",
        "Action": "INVITE",
        "Resources": [
            {
                "Value": "o-kz4vlkihvy",
                "Type": "ORGANIZATION",
                "Resources": [
                    {
                        "Value": "kubernetes-aws-admins@lists.cncf.io",
                        "Type": "MASTER_EMAIL"
                    },
                    {
                        "Value": "Kubernetes AWS Admins",
                        "Type": "MASTER_NAME"
                    },
                    {
                        "Value": "ALL",
                        "Type": "ORGANIZATION_FEATURE_SET"
                    }
                ]
            },
            {
                "Value": "REDACTED",
                "Type": "ACCOUNT"
            }
        ]
    }
}

hh · 2023-01-30T17:35:52Z

sig-release-leads@kubernetes.io is now migrated

hh · 2023-01-30T20:40:42Z

sig-infra-aws-admins+accounts@kubernetes.io (previously: k8s-infra-accounts@kubernetes.io) is now migrated

hh · 2023-01-30T21:13:57Z

k8s-infra-aws-admins+registry-k8s-io@kubernetes.io (previously k8s-infra-aws-registry-k8s-io-admin@kubernetes.io) has an updated email and is ready to migrate: @ameukam I'd like to do this one synchronously

I'd like to get @Riaankl to migrate the remaining accounts *@lists.cncf.io and k8s-infra-aws-admins+*kubernetes.io. The migration process is a bit more streamlined when we have access to everything now.

hh · 2023-01-30T21:14:11Z

/assign @Riaankl

hh · 2023-01-30T21:27:35Z

@mrbobbytables: We will be generating a lot of passwords that need to be saved and likely accessed by #sig-k8s-infra and the sigs these are assigned to. @dims mentioned there is a community 1Password account we should be using. Do you have details?

In support of kubernetes#4626 (comment)

hh · 2023-02-03T01:23:33Z

All but three accounts migrated. Will work to put passwords into 1Password next week.

ameukam · 2023-02-06T21:39:19Z

/area infra/aws
/milestone v1.27

riaankleinhans · 2023-02-07T22:03:25Z

Only account remaining to be migrated is aws-ebs-csi-driver@lists.cncf.io
We do not get the password reset email & link.
@ameukam @dims do you have access to that?

dims · 2023-02-07T22:08:13Z

@Riaankl check with CNCF folks like Amye? if we can figure out who is on that list, we can coordinate with them

riaankleinhans · 2023-02-07T22:10:38Z

@Riaankl check with CNCF folks like Amye? if we can figure out who is on that list, we can coordinate with them

Will do.

riaankleinhans · 2023-02-07T23:24:34Z

@Riaankl check with CNCF folks like Amye? if we can figure out who is on that list, we can coordinate with them

Got that sorted, last account migrated!

ameukam · 2023-02-07T23:51:24Z

@Riaankl check with CNCF folks like Amye? if we can figure out who is on that list, we can coordinate with them

Got that sorted, last account migrated!

@Riaankl if everything is done here, do you mind close this issue ? cc @jeefy @hh

riaankleinhans · 2023-02-08T23:28:26Z

@ameukam I still need to add the passwords for all the accounts in 1password
Think we can close after that. Thanks

riaankleinhans · 2023-02-09T21:03:54Z

All passowrds for the accounts that I migrated was added to the 1password vault AWS CI Accouts
@hh @jeefy @ameukam

/close

k8s-ci-robot · 2023-02-09T21:04:00Z

@Riaankl: Closing this issue.

In response to this:

All passowrds for the accounts that I migrated was added to the 1password vault AWS CI Accouts
@hh @jeefy @ameukam

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

hh · 2023-02-10T00:53:25Z

aws organizations describe-organization

{
    "Organization": {
        "Id": "o-kz4vlkihvy",
        "Arn": "arn:aws:organizations::348685125169:organization/o-kz4vlkihvy",
        "FeatureSet": "ALL",
        "MasterAccountArn": "arn:aws:organizations::348685125169:account/o-kz4vlkihvy/348685125169",
        "MasterAccountId": "348685125169",
        "MasterAccountEmail": "kubernetes-aws-admins@lists.cncf.io",
        "AvailablePolicyTypes": [
            {
                "Type": "SERVICE_CONTROL_POLICY",
                "Status": "ENABLED"
            }
        ]
    }
}

aws organizations list-accounts | jq -r '.Accounts[] | select(.Status="ACTIVE") | .Name + " : " + .Email'  | sort

Kubernetes AWS Admins : kubernetes-aws-admins@lists.cncf.io
aws-ebs-csi-driver Infra : aws-ebs-csi-driver@lists.cncf.io
capa-2020-07-12-01 : k8s-infra-aws-admins+capa-2020-07-12-01@kubernetes.io
capa-2020-07-12-02 : k8s-infra-aws-admins+capa-2020-07-12-02@kubernetes.io
capa-2020-07-13-00 : k8s-infra-aws-admins+capa-2020-07-13-00@kubernetes.io
capa-2020-07-13-01 : k8s-infra-aws-admins+capa-2020-07-13-01@kubernetes.io
capa-2020-07-13-02 : k8s-infra-aws-admins+capa-2020-07-13-02@kubernetes.io
capa-2020-07-13-03 : k8s-infra-aws-admins+capa-2020-07-13-03@kubernetes.io
capa-2020-07-13-04 : k8s-infra-aws-admins+capa-2020-07-13-04@kubernetes.io
capa-2020-07-13-05 : k8s-infra-aws-admins+capa-2020-07-13-05@kubernetes.io
capa-2020-07-13-06 : k8s-infra-aws-admins+capa-2020-07-13-06@kubernetes.io
capa-2020-07-13-07 : k8s-infra-aws-admins+capa-2020-07-13-07@kubernetes.io
capa-2020-07-13-08 : k8s-infra-aws-admins+capa-2020-07-13-08@kubernetes.io
capa-2020-07-13-09 : k8s-infra-aws-admins+capa-2020-07-13-09@kubernetes.io
capa-2020-07-13-10 : k8s-infra-aws-admins+capa-2020-07-13-10@kubernetes.io
capa-2020-07-13-11 : k8s-infra-aws-admins+capa-2020-07-13-11@kubernetes.io
capa-2020-07-13-12 : k8s-infra-aws-admins+capa-2020-07-13-12@kubernetes.io
capa-2020-07-13-13 : k8s-infra-aws-admins+capa-2020-07-13-13@kubernetes.io
capa-2020-11-19-00 : k8s-infra-aws-admins+capa2020111900@kubernetes.io
capa-2020-11-19-01 : k8s-infra-aws-admins+capa2020111901@kubernetes.io
capa-2020-11-19-02 : k8s-infra-aws-admins+capa2020111902@kubernetes.io
capa-2020-11-19-03 : k8s-infra-aws-admins+capa2020111903@kubernetes.io
capa-2020-11-19-04 : k8s-infra-aws-admins+capa2020111904@kubernetes.io
capa-2020-11-19-05 : k8s-infra-aws-admins+capa2020111905@kubernetes.io
capa-2020-11-19-06 : k8s-infra-aws-admins+capa2020111906@kubernetes.io
capa-2020-11-19-07 : k8s-infra-aws-admins+capa2020111907@kubernetes.io
capa-2020-11-19-08 : k8s-infra-aws-admins+capa2020111908@kubernetes.io
capa-2020-11-19-09 : k8s-infra-aws-admins+capa2020111909@kubernetes.io
capa-2020-11-19-10 : k8s-infra-aws-admins+capa2020111910@kubernetes.io
capa-2020-11-19-11 : k8s-infra-aws-admins+capa2020111911@kubernetes.io
capa-2020-11-19-12 : k8s-infra-aws-admins+capa2020111912@kubernetes.io
capa-2020-11-19-13 : k8s-infra-aws-admins+capa2020111913@kubernetes.io
capa-account-00 : k8s-infra-aws-admins+capa-account-00@kubernetes.io
capa-account-01 : k8s-infra-aws-admins+capa-account-01@kubernetes.io
capa-account-02 : k8s-infra-aws-admins+capa-account-02@kubernetes.io
capa-account-03 : k8s-infra-aws-admins+capa-account-03@kubernetes.io
capa-account-04 : k8s-infra-aws-admins+capa-account-04@kubernetes.io
capa-account-05 : k8s-infra-aws-admins+capa-account-05@kubernetes.io
capa-account-06 : k8s-infra-aws-admins+capa-account-06@kubernetes.io
capa-account-07 : k8s-infra-aws-admins+capa-account-07@kubernetes.io
capa-account-08 : k8s-infra-aws-admins+capa-account-08@kubernetes.io
capa-account-09 : k8s-infra-aws-admins+capa-account-09@kubernetes.io
capa-account-2020-02-18-a : k8s-infra-aws-admins+capa-account-2020-02-18-a@kubernetes.io
capa-account-2020-02-18-b : k8s-infra-aws-admins+capa-account-2020-02-18-b@kubernetes.io
capa-account-2020-02-18-c : k8s-infra-aws-admins+capa-account-2020-02-18-c@kubernetes.io
capa-account-2020-02-18-d : k8s-infra-aws-admins+capa-account-2020-02-18-d@kubernetes.io
capa-account-2020-02-18-e : k8s-infra-aws-admins+capa-account-2020-02-18-e@kubernetes.io
capa-account-2020-02-18-f : k8s-infra-aws-admins+capa-account-2020-02-18-f@kubernetes.io
capa-account-2020-02-18-g : k8s-infra-aws-admins+capa-account-2020-02-18-g@kubernetes.io
capa-account-2020-02-18-h : k8s-infra-aws-admins+capa-account-2020-02-18-h@kubernetes.io
capa-account-2020-02-18-i : k8s-infra-aws-admins+capa-account-2020-02-18-i@kubernetes.io
capa-account-2020-02-18-j : k8s-infra-aws-admins+capa-account-2020-02-18-j@kubernetes.io
cncf-k8s-infra-aws-capa-ami : cncf-k8s-infra-aws-capa-ami@lists.cncf.io
cncf-k8s-infra-aws-capa-demo : cncf-k8s-infra-aws-capa-demo@lists.cncf.io
e2e-kops-2020-03-15-a : k8s-infra-aws-admins+e2e-kops-2020-03-15-a@kubernetes.io
e2e-kops-2020-03-15-b : k8s-infra-aws-admins+e2e-kops-2020-03-15-b@kubernetes.io
e2e-kops-2020-03-15-c : k8s-infra-aws-admins+e2e-kops-2020-03-15-c@kubernetes.io
e2e-kops-2020-03-15-d : k8s-infra-aws-admins+e2e-kops-2020-03-15-d@kubernetes.io
image-builder-aws-2020-11-19-00 : k8s-infra-aws-admins+image2020111900@kubernetes.io
image-builder-aws-2020-11-19-02 : k8s-infra-aws-admins+image2020111902@kubernetes.io
image-builder-aws-2020-11-19-03 : k8s-infra-aws-admins+image2020111903@kubernetes.io
image-builder-aws-2020-11-19-04 : k8s-infra-aws-admins+image2020111904@kubernetes.io
image-builder-aws-2020-11-19-05 : k8s-infra-aws-admins+image2020111905@kubernetes.io
image-builder-aws-2020-11-19-06 : k8s-infra-aws-admins+image2020111906@kubernetes.io
image-builder-aws-2020-11-19-07 : k8s-infra-aws-admins+image2020111907@kubernetes.io
image-builder-aws-2020-11-19-08 : k8s-infra-aws-admins+image2020111908@kubernetes.io
image-builder-aws-2020-11-19-09 : k8s-infra-aws-admins+image2020111909@kubernetes.io
image-builder-aws-2020-11-19-10 : k8s-infra-aws-admins+image2020111910@kubernetes.io
image-builder-aws-2021-03-28-01 : k8s-infra-aws-admins+image2021032801@kubernetes.io
image-builder-aws-2021-25-03/28/21-01 : k8s-infra-aws-admins+image20212503/28/2101@kubernetes.io
k8s-infra-artifacts-k8s-io-prod : k8s-infra-aws-admins+artifacts-k8s-io-prod@kubernetes.io
k8s-infra-aws-admins+accounts : k8s-infra-aws-admins+accounts@kubernetes.io
k8s-infra-aws-admins+registry-k8s-io : k8s-infra-aws-admins+registry-k8s-io@kubernetes.io
k8s-infra-aws-root-account : k8s-infra-aws-root-account@kubernetes.io
k8s-infra-networking : k8s-infra-aws-admins+infra-networking@kubernetes.io
k8s-infra-organisation-incident-response : k8s-infra-aws-admins+incident-response@kubernetes.io
k8s-infra-organisation-logging : k8s-infra-aws-admins+logging@kubernetes.io
k8s-infra-organisation-security : k8s-infra-aws-admins+security@kubernetes.io
k8s-infra-registry-k8s-io-prod : k8s-infra-aws-admins+registry-k8s-io-prod@kubernetes.io
k8s-infra-security-audit : k8s-infra-aws-admins+security-audit@kubernetes.io
k8s-infra-security-engineering : k8s-infra-aws-admins+security-engineering@kubernetes.io
k8s-infra-security-incident-response : k8s-infra-aws-admins+security-incident-response@kubernetes.io
k8s-infra-security-logs : k8s-infra-aws-admins+artifacts-k8S-io@kubernetes.io
k8s-infra-security-logs : k8s-infra-aws-admins+security-logs@kubernetes.io
k8s-infra-shared-services : k8s-infra-aws-admins+infra-network@kubernetes.io
k8s-infra-shared-services : k8s-infra-aws-admins+infra-shared-services@kubernetes.io
sig-release-leads : sig-release-leads@kubernetes.io

jeefy · 2023-04-07T19:50:52Z

Looks like some were missed, filed #5111 to capture that effort, but linking here as well.

hh added area/dns DNS records for k8s.io, kubernetes.io, k8s.dev, etc., code in dns/ sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. labels Jan 13, 2023

hh changed the title ~~Tracking Kubernetes AWS Account Migrations from CNCF~~ Tracking 73 Kubernetes AWS Account Migrations from CNCF Jan 13, 2023

hh added a commit to hh/k8s.io that referenced this issue Jan 18, 2023

Add cncf-aws-admins@lists.cncf.io to k8s-infra

0288c1d

Part of kubernetes#4626 (comment)

hh mentioned this issue Jan 18, 2023

Add cncf-aws-admins@lists.cncf.io to k8s-infra #4645

Merged

hh mentioned this issue Jan 18, 2023

Adding cncf-aws-admins to sig-release-leads #4646

Closed

hh mentioned this issue Jan 19, 2023

Migrate first three AWS kubernetes.io accounts from CNCF to Kubernetes #4658

Closed

8 tasks

k8s-ci-robot assigned riaankleinhans Jan 30, 2023

hh added a commit to hh/k8s.io that referenced this issue Jan 31, 2023

Add k8s-infra-ii-coop to k8s-infra-aws-admins

58654f0

In support of kubernetes#4626 (comment)

hh mentioned this issue Jan 31, 2023

Add k8s-infra-ii-coop to k8s-infra-aws-admins #4702

Merged

k8s-ci-robot added the area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure label Feb 6, 2023

k8s-ci-robot added this to the v1.27 milestone Feb 6, 2023

k8s-ci-robot closed this as completed Feb 9, 2023

hh closed this as completed Feb 10, 2023

hh mentioned this issue Jun 7, 2023

REQUEST: Need for AWS account for hosting CAPA generated AMIs #5010

Open

ameukam mentioned this issue Sep 13, 2023

[Umbrella issue] cleanup AWS organization #5844

Closed

3 tasks

ameukam mentioned this issue Oct 14, 2023

AWS: Ensure CloudTrail is enabled for the Organization #4682

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tracking 73 Kubernetes AWS Account Migrations from CNCF #4626

Tracking 73 Kubernetes AWS Account Migrations from CNCF #4626

hh commented Jan 13, 2023 •

edited

Loading

hh commented Jan 16, 2023 •

edited

Loading

hh commented Jan 16, 2023

hh commented Jan 17, 2023

hh commented Jan 17, 2023

dims commented Jan 17, 2023

hh commented Jan 17, 2023 •

edited

Loading

hh commented Jan 17, 2023 •

edited

Loading

upodroid commented Jan 17, 2023

hh commented Jan 18, 2023

upodroid commented Jan 18, 2023

hh commented Jan 18, 2023

hh commented Jan 18, 2023 •

edited

Loading

ameukam commented Jan 18, 2023

ameukam commented Jan 18, 2023

hh commented Jan 18, 2023

ameukam commented Jan 18, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023 •

edited

Loading

hh commented Feb 3, 2023

ameukam commented Feb 6, 2023

riaankleinhans commented Feb 7, 2023

dims commented Feb 7, 2023

riaankleinhans commented Feb 7, 2023

riaankleinhans commented Feb 7, 2023

ameukam commented Feb 7, 2023

riaankleinhans commented Feb 8, 2023

riaankleinhans commented Feb 9, 2023

k8s-ci-robot commented Feb 9, 2023

hh commented Feb 10, 2023

jeefy commented Apr 7, 2023

Tracking 73 Kubernetes AWS Account Migrations from CNCF #4626

Tracking 73 Kubernetes AWS Account Migrations from CNCF #4626

Comments

hh commented Jan 13, 2023 • edited Loading

Kubernetes OU (3)

registry.k8s.io OU (1)

aws-ebs-csi-driver OU (1)

kops OU (4)

sig-k8s-infra OU (12)

capa OU (52)

hh commented Jan 16, 2023 • edited Loading

hh commented Jan 16, 2023

Effects of removing an account from an organization

hh commented Jan 17, 2023

hh commented Jan 17, 2023

dims commented Jan 17, 2023

hh commented Jan 17, 2023 • edited Loading

hh commented Jan 17, 2023 • edited Loading

Steps:

upodroid commented Jan 17, 2023

hh commented Jan 18, 2023

upodroid commented Jan 18, 2023

hh commented Jan 18, 2023

hh commented Jan 18, 2023 • edited Loading

ameukam commented Jan 18, 2023

ameukam commented Jan 18, 2023

hh commented Jan 18, 2023

ameukam commented Jan 18, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023

hh commented Jan 30, 2023 • edited Loading

hh commented Feb 3, 2023

ameukam commented Feb 6, 2023

riaankleinhans commented Feb 7, 2023

dims commented Feb 7, 2023

riaankleinhans commented Feb 7, 2023

riaankleinhans commented Feb 7, 2023

ameukam commented Feb 7, 2023

riaankleinhans commented Feb 8, 2023

riaankleinhans commented Feb 9, 2023

k8s-ci-robot commented Feb 9, 2023

hh commented Feb 10, 2023

jeefy commented Apr 7, 2023

hh commented Jan 13, 2023 •

edited

Loading

hh commented Jan 16, 2023 •

edited

Loading

hh commented Jan 17, 2023 •

edited

Loading

hh commented Jan 17, 2023 •

edited

Loading

hh commented Jan 18, 2023 •

edited

Loading

hh commented Jan 30, 2023 •

edited

Loading