LoadBalancerConfiguration CRD missing spec.vpcId

[mlflr]

Bug Description
Documentation refers to a spec.vpcId option of LoadBalancerConfiguration here and here but that option is missing from the CRD

Steps to Reproduce
Try to apply following resource

apiVersion: gateway.k8s.aws/v1beta1
kind: LoadBalancerConfiguration
metadata:
  name: test-lb-config
spec:
  vpcId: vpc-XXXX

Expected Behavior
Resource is created with the vpcId option as per documentation

Actual Behavior
error failed to create typed patch object (namespace/name; gateway.k8s.aws/v1beta1, Kind=LoadBalancerConfiguration): .spec.vpcId: field not declared in schema.

spec.vpcId is not defined in https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/refs/heads/main/config/crd/gateway/gateway-crds.yaml

Regression
Was the functionality working correctly in a previous version ? Not sure/Have not tested

Current Workarounds
No workarounds available

Environment

• AWS Load Balancer controller version: 3.3.0
• Kubernetes version: 1.33.10
• Using EKS (yes), if so version?: 1.33
• Using Service or Ingress: Gateway API
• AWS region: eu-west-1
• How was the aws-load-balancer-controller installed: not relevant
• Current state of the Controller configuration: not relevant
• Current state of the Ingress/Service configuration: not relevant

Possible Solution (Optional)
Update the CRD if supported in code or remove from current documentation if unsupported to prevent confusion

Contribution Intention (Optional)

• Yes, I'm willing to submit a PR to fix this issue
• No, I cannot work on a PR at this time

Additional Context

[dominikhei]

I just checked the relevant CRD and the type definition and the vpcID is missing. It just exists as a global controller flag.

Is there a reason it is not implemented but documented?

[shraddhabang]

I think this is a documentation error. We follow the similar way of using global controller flag to set the vpcId. We will fix ths doc error.

[dominikhei]

I think this is a documentation error. We follow the similar way of using global controller flag to set the vpcId. We will fix ths doc error.

Hope it's fine if I raise a PR for this, had some spare time. Let me know if you'd prefer to handle it yourselves and I'll close it.

[mlflr]

From my point of view, that is a bit disappointing. Controller flag is not enough. There are cases when you need to manage LBs across multiple VPCs. For example having public LBs in a separate egress VPC and internal LBs in a different one.