Contour 1.0.0-rc.2 is the second, and hopefully final, release candidate on the path to Contour 1.0. Assuming that no serious issues are found next week we’re on track to release Contour 1.0 on November 1st.
It goes without saying that without the help of the many community contributors this release, nor the 38 that preceded it, would not have been possible. Thank you all.
You can read the full 1.0.0-rc.2 release notes over on GitHub, but as you’re here, here are a few highlights.
As part of the continued preparations for the 1.0 release Contour’s documentation has been relocated to the projectcontour.io website. Specifically;
We’re working hard to polish the website content ahead of the 1.0 release. Please pardon our dust.
IngressRoute and HTTPProxy status updates are now performed by the lead Contour in the deployment. We’re hopeful that this will put to rest the many issues related to status update loops over the years.
Contour 1.0.0-rc.2 includes updated OpenAPIv3 schema validations. These schemas are automatically generated from the CRDs themselves and should be more complete and consistent than the previous hand rolled versions.
Contour 1.0.0-rc.2 now supports TCPProxy delegation. See the relevant section in the HTTPProxy documentation.
Contour 1.0.0-rc.2 configures various keep alive mechanisms to detect network connectivity issues between Envoy and Contour. This helps Contour and Envoy work better with overlay networks which drop long running idle TCP connections.
Contour now delays serving traffic to Envoy until each of the API informers caught up to the API server. This changes reduces the likelihood that Envoy can connect to a Contour instance in the process of startup and thus observe an incomplete view of the cluster.
Please consult the Upgrading document for information on upgrading from Contour 1.0.0-rc.1 to Contour 1.0.0-rc.2.