James Peach

> Looking at this quickly it feels like the right approach is to add a `OnReady` cb on the component api and have the component manager do the link between...

Prerequisite for #1944

Blocked by #403

See: https://github.com/kubernetes-sigs/ingress-controller-conformance And a separate effort: https://github.com/aledbf/ingress-conformance

Ingress conformance is basically blocked. There's no agreement upstream on what the harness should look like, so verification checks can't be committed.

Removing this from the prioritize backlog because it is blocked upstream.

> @jpeach i would prefer we add the blocked tag and leave it in the backlog. we still want to do it at the current priority or as soon as...

> Does this still look blocked given the state of https://github.com/kubernetes-sigs/ingress-controller-conformance? (theres some example of running conformance with sonobuoy and kind etc. https://github.com/kubernetes-sigs/ingress-controller-conformance/blob/master/examples/kind/.github/workflows/main.yaml) See https://github.com/projectcontour/contour/issues/1944

@sunjayBhatia IIRC at least some of these tests are for ingress V1, which isn't implemented in Contour.

FWIW, xDS client validation is: ``` "verify_subject_alt_name": [ "contour" ] ```