Is there a way to implement group.order similar to the ingress for AWS ALB in the Gateway API?

[deep5777]

scheme: internet-facing → LoadBalancerConfiguration.spec.scheme
certificate-arn → LoadBalancerConfiguration.spec.listenerConfigurations[].certificates
ssl-policy → LoadBalancerConfiguration.spec.listenerConfigurations[].sslPolicy
wafv2-acl-arn → LoadBalancerConfiguration.spec.wafV2.webACL
listen-ports → LoadBalancerConfiguration.spec.listenerConfigurations[].protocolPort
target-type → TargetGroupConfiguration.spec.defaultConfiguration.targetType
backend-protocol → TargetGroupConfiguration.spec.defaultConfiguration.protocol
healthcheck-* → TargetGroupConfiguration.spec.defaultConfiguration.healthCheckConfig.*
success-codes → TargetGroupConfiguration.spec.defaultConfiguration.healthCheckConfig.matcher.httpCode
actions.* (fixed + source-ip conditions) → ListenerRuleConfiguration.spec.actions[].fixedResponseConfig
→ ListenerRuleConfiguration.spec.conditions[].sourceIPConfig
actions.* (redirects) → HTTPRoute.spec.rules[].filters[].requestRedirect
group.order / order → NOT SUPPORTED

Most annotations will be handled by CRDs or Gateway API filtering, but we’re holding off on group order as I don’t see a viable solution. Do you have any suggestions?