add sts regional endpoint logic

[prasita123]

What type of PR is this?

kind bug

What this PR does / why we need it:
STS suggests using regional endpoints. (source)

AWS recommends using Regional STS endpoints to reduce latency, build in redundancy, and increase session token validity.

The PR uses sts regional endpoints, fetched using the metadata, instead of global endpoints.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Updates to the cloud-controller-manager to use regional endpoint instead of global endpoint, as AWS recommends using Regional STS endpoints to reduce latency, build in redundancy, and increase session token validity.

[k8s-ci-robot]

Welcome @prasita123!

It looks like this is your first PR to kubernetes/cloud-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/cloud-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @prasita123. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[wongma7]

since this is almost identical to the passage

cloud-provider-aws/pkg/providers/v1/aws.go

Lines 1300 to 1317 in 8cdf512

	metadata, err := awsServices.Metadata()
	if err != nil {
	return nil, fmt.Errorf("error creating AWS metadata client: %q", err)
	}
	err = updateConfigZone(&cfg, metadata)
	if err != nil {
	return nil, fmt.Errorf("unable to determine AWS zone from cloud provider config or EC2 instance metadata: %v", err)
	}
	zone := cfg.Global.Zone
	if len(zone) <= 1 {
	return nil, fmt.Errorf("invalid AWS zone in config file: %s", zone)
	}
	regionName, err := azToRegion(zone)
	if err != nil {
	return nil, err
	}

could you refactor that to also use this function?

[wongma7]

/ok-to-test

[wongma7]

newline is needed her.

Run ./hack/verify-gofmt.sh locally to verify.

ref: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/cloud-provider-aws/313/pull-cloud-provider-aws-check/1499213287563202560

[wongma7]

consider returning multiple return values like

(string, string, err)
region, zone, err 

instead. I like it better than a special struct

[wongma7]

must check for err here

[wongma7]

I think the lack of err check causes TestNewAWSCloud to fail now after the refactor, try the test locally as well to verify .. https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/cloud-provider-aws/313/pull-cloud-provider-aws-test/1499235237555605504

[wongma7]

/test pull-cloud-provider-aws-e2e

[wongma7]

/retest

[nckturner]

/test pull-cloud-provider-aws-e2e

[prasita123]

tested the change on a v1.22 cluster (manifest bd810fe3d5ba620f3d7cad5e4b40c11bc6efa1471d2e5075f459d29f48dca745)

• validated the sts endpoint on a newly launched instance by terminating an existing node instance of the cluster

"tlsDetails": {
        "tlsVersion": "TLSv1.2",
        "cipherSuite": "ECDHE-RSA-AES128-GCM-SHA256",
        "clientProvidedHostHeader": "sts.us-west-2.amazonaws.com"
    }

https://tiny.amazon.com/a7l9nrne/IsenLink

[wongma7]

/lgtm
but does it need a release note? maybe yes for the miniscule non-zero chance somebody has not enabled regional endpoint in opt-in region? if not put NONE in the field at the bottom of PR description

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: prasita123, wongma7

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:

• OWNERS [wongma7]

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

[nckturner]

Yeah let's add one. Which reminds me... we need some mechanism to get release notes out of this don't we? I'm assuming that is buried in the kubernetes release automation but doesn't apply to other repositories.

[wongma7]

not sure it is usable outside k/k but https://github.com/kubernetes/sig-release/blob/d30b2484d7b18f869dd7f560ef5fb52a3b536a32/release-team/role-handbooks/release-notes/editing-flow.md#workflow-operation .

@prasita123 plz draft a release note, we can review that as well

[nckturner]

/test pull-cloud-provider-aws-check

[nckturner]

/test pull-cloud-provider-aws-check