You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know it sounds like lunacy but there are non-standard AWS regions in which Kubernetes might be deployed (e.g. Eucalyptus). Instead of enumerating each zone in pkg/credentialprovider/aws/aws_credentials.go, perhaps it would be appropriate to add a flag in a configuration file to disable the check.
The region validation would be enabled by default, handling the vast majority of cases. In the edge case that region validation is undesirable, this flag would provide a workaround.
The text was updated successfully, but these errors were encountered:
Automatic merge from submit-queue
AWS: Added experimental option to skip zone check
This pull request resolves#28380. In the vast majority of cases, it is appropriate to validate the AWS region against a known set of regions. However, there is the edge case where this is undesirable as Kubernetes may be deployed in an AWS-like environment where the region is not one of the known regions.
By adding the optional **DisableStrictZoneCheck true** to the **[Global]** section in the aws.conf file (e.g. /etc/aws/aws.conf) one can bypass the ragion validation.
I know it sounds like lunacy but there are non-standard AWS regions in which Kubernetes might be deployed (e.g. Eucalyptus). Instead of enumerating each zone in pkg/credentialprovider/aws/aws_credentials.go, perhaps it would be appropriate to add a flag in a configuration file to disable the check.
The region validation would be enabled by default, handling the vast majority of cases. In the edge case that region validation is undesirable, this flag would provide a workaround.
The text was updated successfully, but these errors were encountered: