github/k3s - k3s - https://git.xinac.net

Commit Graph

Author	SHA1	Message	Date
Bryce Carman	3b99e1b487	Add AWS cloud provider option for IAM role Currently the AWS cloud provider uses the EC2 instance role when interacting with AWS APIs. This change gives the option to provide and IAM role that the cloud provider will assume before calling the APIs. All resources created by the role will be owned by that account instead of the account where the EC2 instance is running.	2018-02-15 21:14:58 -08:00
Robert Rati	aa8e14d4fe	Moved fakes to a separate file usable by other tests	2017-09-22 13:30:05 -04:00
Justin Santa Barbara	04b787b946	AWS: trust region if found from AWS metadata Means we can run in newly announced regions without a code change. We don't register the ECR provider in new regions, so we will still need a code change for now. This also means we do trust config / instance metadata, and don't reject incorrectly configured zones. Fix #35014	2017-01-18 09:17:55 -05:00

Author

SHA1

Message

Date

Bryce Carman

3b99e1b487

Add AWS cloud provider option for IAM role

Currently the AWS cloud provider uses the EC2 instance role when
interacting with AWS APIs. This change gives the option to provide and IAM
role that the cloud provider will assume before calling the APIs. All
resources created by the role will be owned by that account instead of
the account where the EC2 instance is running.

2018-02-15 21:14:58 -08:00

Robert Rati

aa8e14d4fe

Moved fakes to a separate file usable by other tests

2017-09-22 13:30:05 -04:00

Justin Santa Barbara

04b787b946

AWS: trust region if found from AWS metadata

Means we can run in newly announced regions without a code change.

We don't register the ECR provider in new regions, so we will still need
a code change for now.

This also means we do trust config / instance metadata, and don't reject
incorrectly configured zones.

Fix #35014

2017-01-18 09:17:55 -05:00

3 Commits (50c5b379b7ff7f980b0318d89a2e4fd02ccfa916)