Update aws-network-topology-operator
to allow targeting specific subnets
#1865
Labels
area/kaas
Mission: Cloud Native Platform - Self-driving Kubernetes as a Service
kind/task
provider/cluster-api-aws
Cluster API based running on AWS
topic/capi
Currently TGW attachments will attach into the first subnet found for each availability zone.
The operator should be updated to support first checking for subnets tagged with
subnet.giantswarm.io/tgw-attachments: "true"
and if not found then fall back to the first found as it currently does.This same logic was recently added to the
aws-vpc-operator
in this PR - giantswarm/aws-vpc-operator#22The text was updated successfully, but these errors were encountered: