Skip to content
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

Add regions ap-northeast-3 and eu-west-3 to AWS cloud provider #70252

Merged
merged 1 commit into from
Oct 26, 2018

Conversation

nckturner
Copy link
Contributor

What type of PR is this?
/kind feature
/sig aws

What this PR does / why we need it:
Add regions ap-northeast-3 and eu-west-3 to the list of well known AWS regions.

Does this PR introduce a user-facing change?:
NONE. The aws cloudprovider can discover unknown regions from instance metadata. Although, in the case that we are not running on an ec2 instance and have not configured a region, but still need to validate whether a region is correct, then we can validate these newer regions correctly, though I don't know when this would happen.

Add regions ap-northeast-3 and eu-west-3 to the list of well known AWS regions.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. sig/aws size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 25, 2018
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. labels Oct 25, 2018
@nckturner nckturner changed the title Add regions ap-northeast-3 and eu-west-3 Add regions ap-northeast-3 and eu-west-3 to AWS cloud provider Oct 25, 2018
@justinsb
Copy link
Member

/approve
/lgtm

/retest

And FYI it happens on the ECR validation - without this PR, an instance in another region won't recognize an ECR image in e.g. ap-northeast-3.

(I'm not entirely sure why we don't do a DescribeRegions call though... I think it's because it wasn't in the kube-up AWS IAM policy, though I think kops has it for other reasons)

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 26, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb, nckturner

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

The pull request process is described here

Needs approval from an approver in each of these files:

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 26, 2018
@k8s-ci-robot k8s-ci-robot merged commit 7147138 into kubernetes:master Oct 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants