Closed JunjieTang-D1 closed 3 weeks ago
We will take a look and evaluate LOE
@JunjieTang-D1 It appears that once the VPC in the region is configured to support a LocalZone, you just reference the subnet and all still works (EKS itself would probably need a self-managed node group in order to leverage the LZ, but that is not SF's concern).
I don't understand this comment, though:
I'm always frustrated when I have to deploy a piece of CDK code e.g. EKS cluster to the Hamburg LocalZone, from the AWS Frankfurt region.
I am not sure I understand this as the LZ must be associated with a VPC in a region. Though I understand your use case, I am not understanding your request. The LZ cannot exist without the region, so CDK code must be deployed in the region.
This has been vetted that SF can deploy to LZ's as-is. The configuration of modules to leverage LZ's is up to the developers
Is your feature request related to a problem? Please describe. I'm always frustrated when I have to deploy a piece of CDK code e.g. EKS cluster to the Hamburg LocalZone, from the AWS Frankfurt region.
Describe the solution you'd like Here is the architecture of seed-farmer and code-seed. The step 2 to 6 will run in the Frankfurt region. Only the deployment target in step 7 e.g. CDK for EKS clusters is the Hamburg LocalZone
Describe alternatives you've considered There is no alternative solution to make a consistent developer experience.