RouteTable Subnet Assocation Selector support for multiple subnets

[enderv]

What problem are you facing?

For RouteTables if you are using the subnetIdSelector in associations you must list multiple associations to get multiple subnets. Ideally you would be able to get all matches in one reference instead of having to make each subnet with unique labels so you can reference them.

Current example from composition I am building:

kind: RouteTable
spec:
  forProvider:
    tags:
      - key: Name
    vpcIdSelector:
      matchControllerRef: true
    routes:
      - destinationCidrBlock: 0.0.0.0/0
        gatewayIdSelector:
          matchControllerRef: true
    associations:
      - subnetIdSelector:
          matchLabels:
            visibility: public
            zone: zoneA
      - subnetIdSelector:
          matchLabels:
            visibility: public
            zone: zoneB
  deletionPolicy: Delete

Ideally it would be something like this and for this example get all public labeled subnets in the composition.

apiVersion: ec2.aws.crossplane.io/v1beta1
kind: RouteTable
spec:
  forProvider:
    tags:
      - key: Name
    vpcIdSelector:
      matchControllerRef: true
    routes:
      - destinationCidrBlock: 0.0.0.0/0
        gatewayIdSelector:
          matchControllerRef: true
    associations:
      - subnetIdSelector:
          matchControllerRef: true
          matchLabels:
            visibility: public

How could Crossplane help solve your problem?

[MisterMX]

This will be difficult to implement as every item in spec.forProvider.associations stores only a single subnetId which makes it difficult to track multiple subnets without altering the whole array and risking an update loop with existing MRs.

Closing this now since I highly doubt that this will be implemented.

[pjanouse]

I'm coming here because I've been dealing with the same issue... My idea was that Subnet selection based on its label(s) works like a filter and each Subnet which qualifies will have attached this RouteTable instead of implicit one.

In current form this doesn't make sense - the deployment can be a dynamic and more subnets can be attached to VPC over the time... in that case I need a simple mechanism how to say Crossplane which Subnet should have which RouteTable (with proper Policy) - currently matching by unique label(s) or unique name is equivalent way without any additional value... In both cases I need one matching block per Subnet currently.

[pjanouse]

More over its pretty confusing - compare

RouteTable:
https://doc.crds.dev/github.com/crossplane/provider-aws/ec2.aws.crossplane.io/RouteTable/[email protected]#spec-forProvider-associations-subnetIdSelector

versus

Cluster (EKS):
https://doc.crds.dev/github.com/crossplane/provider-aws/eks.aws.crossplane.io/Cluster/[email protected]#spec-forProvider-resourcesVpcConfig-subnetIdSelector
or
NodeGroup:
https://doc.crds.dev/github.com/crossplane/provider-aws/eks.aws.crossplane.io/NodeGroup/[email protected]#spec-forProvider-subnetSelector

Please reconsider your statement and provide a better (I mean consistent) UX...