Gateway 1.0 Support

[mpstefan]

Background

Gateway API 1.0 is targeting a release in approximately two weeks, just before KubeCon. To ensure we keep up to date on Gateway releases, we need to implement the changes necessary to pass conformance for 1.0.

Acceptance Criteria

• Conformance tests for Gateway 1.0 all pass.

For Discussion

• Is conformance the only metric we need to pay attention to?
• What conformance tests will break? How can we tell?

Tasks

Preview Give feedback

1. HTTPRoute partial validity #485
   area/httproute/core enhancement refined size/extra-small +4
   
2. Use official Gateway API PartiallyInvalid condition #1168
   blocked enhancement refined size/extra-small tracking +5
   
3. Conform to Gateway spec for AttachedRoutes of Gateway #1148
   bug refined size/medium +3
   
4. Test Gateway API 1.0.0 rc 1 #1144
   conformance refined size/small tests +4
   
5. Update resource validation docs to cover CEL #971
   documentation refined size/small +3
   
6. Ensure oldest supported Kubernetes version is using webhooks for nightly conformance tests #1183
   refined size/extra-small tests +3
   
7. SupportedVersion condition for GatewayClass #1178
   enhancement refined size/small +3
   
8. Upgrade to Gateway API v1.0.0 #1230
   dependencies enhancement refined size/small +4