rancher
Use API to get EKS region and instance data instead of hardcoding
The UI has a fair bit of hardcoded amazon data, see: https://github.com/rancher/ui/blob/master/lib/shared/addon/utils/amazon.js In particular we are manually keeping track of which EKS versions to show. We should investigate whether or not there is an API we can use for EKS versions and possibly region/instance data as well.
Someone found a way to do it indirectly https://stackoverflow.com/a/71448603/5370501
There is already an issue about replacing the hardcoded EKS versions https://github.com/rancher/dashboard/issues/4401, so I'm editing the scope of the issue to region and instance data.
Related backend issue for EKS versions is here https://github.com/rancher/rancher/issues/33766
Also for reference, there is a SUSE project https://github.com/SUSE-Enceladus/aws-regions - this uses the AWS CLI project on GitHub - https://github.com/boto/botocore - looks like it maintains up to date data that could be used: https://github.com/boto/botocore/blob/develop/botocore/data/endpoints.json
For 2.7.next2, we should maybe spend size/5 on this so we need to estimate the effort here; if it's larger, then we push it out. But this would help with a regular series of requests we get.
Need to also consider EC2 regions and regions list used when supplying credentials
This covers old and new UIs.
Old UI REGIONS - Used for EC2 AND credentials (used by both ec2 and eks) EKS_REGIONS - Used for eks things
New UI TBD
@mantis-toboggan-md when we port EKS, is this doable in Vue? or is that even possible? We could potentially close this if this is also covered with existing migration plans.
@gaktive I think it would make sense to tackle this at the same time as the EKS migration, but I don't think this enhancement is implicit in that plan - it's worth calling out directly. It wouldn't be any harder in Vue than Ember.
