Mattia Lavacca

Addressed by #3458 /reopen /remove-lifecycle rotten

> [@mlavacca](https://github.com/mlavacca) Is this resolved after [#3458](https://github.com/kubernetes-sigs/gateway-api/pull/3458) has been merged? It's not yet. #3458 updated only the GEP, while this is about updating the documentation. I think we should address...

This one is in a similar situation as https://github.com/kubernetes-sigs/gateway-api/pull/2821. We'd need https://github.com/kubernetes-sigs/gateway-api/issues/3009 to be addressed before adding conformance tests on feature not implemented yet by any project.

We already have a test to check that `HTTPRoute`s with non-existent `backendRefs` get the proper `ResolvedRefs` condition. As said by @youngnick, all the implementations need to trigger reconciliation loops upon...

Yep, as @youngnick confirmed, we are willing to support Terminate for `TLSRoute` with #3458. However, we cannot consider it ready until conformance tests are added for this feature. An issue...

/triage accepted

/remove-lifecycle rotten

> Invalid: both CACertificateRef and WellKnownCACertificates is specified I think this test cannot be implemented, as this rule is directly enforced by CEL: https://github.com/kubernetes-sigs/gateway-api/blob/d49ae960279b7022c8f7e041221df306ef64094d/apis/v1alpha3/backendtlspolicy_types.go#L81

> Valid BackendTLSPolicy with 1 targetRef/service using WellKnownCACertificates and matching hostname `WellKnownCACertificates` is an implementation-specific feature, therefore I think we should either: - leave it out of conformance tests, or...

> Invalid: targetRef in different namespace The TargetRef is a `LocalPolicyTargetReference`, there is no namespace field in it. I think that a `TargetRef` in a different namespace is impossible, given...