Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update aws-network-topology-operator to allow targeting specific subnets #1865

Closed
AverageMarcus opened this issue Jan 16, 2023 · 1 comment
Closed
Assignees
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

Comments

@AverageMarcus
Copy link
Member

AverageMarcus commented Jan 16, 2023

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#22

@AverageMarcus AverageMarcus changed the title Update aws-network-topology-operator to allow targeting specific subnets Update aws-network-topology-operator to allow targeting specific subnets Jan 16, 2023
@alex-dabija alex-dabija added area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service team/hydra topic/capi provider/cluster-api-aws Cluster API based running on AWS kind/task labels Jan 17, 2023
@bdehri bdehri self-assigned this Jan 17, 2023
@bdehri
Copy link

bdehri commented Jan 26, 2023

@bdehri bdehri closed this as completed Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

3 participants