IngressRoute removal in Contour 1.6

[Nick Young]

Hi everyone,

This is the official announcement that support for the deprecated IngressRoute objects will be removed in Contour 1.6.

This means that:

- IngressRoute objects will no longer be watched by Contour, and config in them will not produce any changes in Envoy.

- TLSCertificateDelegations using the contour.heptio.com apigroup will also no longer be watched by Contour.

- The install YAMLs for Contour will no longer include any of the contour.heptio.com CRDs.

- The CRDs will be removed from the repo as well (you can use the v1.5.0 tag to pull copies of them if you need to).

We've made available the ir2proxy tool (https://github.com/projectcontour/ir2proxy) to help with converting IngressRoute objects to HTTPProxy ones.

ir2proxy should support all IngressRoute options, as far as possible. Some IngressRoute configurations require manual intervention - the tool will tell you if that's the case.

If there are cases that are not supported, please log an issue at https://github.com/projectcontour/ir2proxy/issues/new/choose.

Please also ask questions on #contour on the Kubernetes slack if you need more help.

Thanks,

Nick Young

Contour Tech Lead