expand to all S3 regions for registry.k8s.io

[upodroid]

Part of #8818

Couple of notes:

1. I opted all the new regions in to the AWS account
2. Terraform AWS provider v6 handles multi region much better as the resources have region parameter and there is no need for regional providers.
3. I started backfilling the buckets with using AWS Datasync for af-south1. I'll be doing the rest with terraform.
4. The state was stored in a CNCF account I can't access so I regenerate it.
5. Enforcing BucketOwner disables ACLs so I got rid of aws_s3_bucket_acl
6. me-south-1 broke since I opened this PR so I commented it out, the infra exists though
7. I created a prod cdn endpoint that will serve all traffic not from AWS.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: upodroid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• infra/aws/OWNERS [upodroid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@upodroid: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-k8sio-verify	6d1e3b1	link	true	/test pull-k8sio-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

Details

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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-sigs/prow repository.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: upodroid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• infra/aws/OWNERS [upodroid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-infra-ci-robot]

Ran Plan for 2 projects:

1. dir: infra/aws/terraform/registry.k8s.io workspace: default
2. dir: infra/aws/terraform/registry.k8s.io/s3 workspace: default

---

1. dir: infra/aws/terraform/registry.k8s.io workspace: default

Plan Error

running 'sh -c' '/atlantis/bin/terraform1.15.8 init -input=false -upgrade' in '/atlantis/repos/kubernetes/k8s.io/8819/default/infra/aws/terraform/registry.k8s.io': exit status 1
Initializing the backend...

╷
│ Error: Error refreshing state: Unable to access object "terraform.tfstate" in S3 bucket "k8s-infra-registry-k8s-io-tfstate": operation error S3: HeadObject, https response error StatusCode: 403, RequestID: 97Q6R2VK8S7TAA9E, HostID: fRK0YcnoxIoK2sZBbnvCFwnbpOEJtV+QUA0Q/63qvFqG+/Fo23AaUAFMzgobdoqqVNF+I5H6xjZoN/+gAXl3/GlXTVe+rcsO, api error Forbidden: Forbidden
│ 
│ 
╵

---

2. dir: infra/aws/terraform/registry.k8s.io/s3 workspace: default

Plan Error

running 'sh -c' '/usr/local/bin/terraform plan -input=false -refresh -out "/atlantis/repos/kubernetes/k8s.io/8819/default/infra/aws/terraform/registry.k8s.io/s3/default.tfplan"' in '/atlantis/repos/kubernetes/k8s.io/8819/default/infra/aws/terraform/registry.k8s.io/s3': exit status 1
╷
│ Error: No value for required variable
│ 
│   on variables.tf line 34:
│   34: variable "region" {
│ 
│ The root module input variable "region" is not set, and has no default
│ value. Use a -var or -var-file command line argument to provide a value for
│ this variable.
╵

---

Plan Summary

2 projects, 0 with changes, 0 with no changes, 2 failed

• ⏩ To apply all unapplied plans from this Pull Request, comment:

  atlantis apply

• 🚮 To delete all plans and locks from this Pull Request, comment:

  atlantis unlock