Remove hard failure for not getting global STS endpoint

aws / amazon-vpc-resource-controller-k8s

Controller for managing Trunk & Branch Network Interfaces on EKS Cluster using Security Group For Pod feature and IPv4 Addresses for Windows Node.

Apache License 2.0

79 stars 53 forks source link

Closed jaydeokar closed 3 weeks ago

jaydeokar commented 3 weeks ago

Issue #, if available: N/A

Description of changes: We don't use global STS endpoint so in case global endpoint is not found, ignore and move ahead with regional STS provider

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

orsenthil commented 3 weeks ago

We don't use global STS endpoint so in case global endpoint is not found, ignore and move ahead with regional STS provider

This needs to be tested for other regions.

I think, we rely on global endpoint if the regional endpoint is not available. But post merge is fine.