OSDOCS-1837: Release note for Ingress TLS 1.3 support

[skrthomas]

https://issues.redhat.com/browse/OSDOCS-1837

For 4.9

Preview: https://deploy-preview-36649--osdocs.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-9-release-notes?utm_source=github&utm_campaign=bot_dp#ocp-4-9-networking

@miheer ready for review.

[netlify]

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: 42c63b4

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/61609f8c7d7c4e0007039a17

😎 Browse the preview: https://deploy-preview-36649--osdocs.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-9-release-notes

[miheer]

@skrthomas

In the product documentation for OCP 4.9, please search and delete statements that TLSv1.3 is not supported.

We also want to release notes in OCP 4.6, 4.7, 4.8 as follows -

In OCP 4.6, 4.7 and 4.8,

The “Modern” profile will continue to be unsupported on OpenShift 4.6, 4.7, and 4.8; selecting it will continue to have the effect of enabling the “Intermediate” profile.
Specifying TLSv1.3 cipher suites in Custom Profile will continue to have no effect; OpenShift router will enable Red Hat distributed OpenSSL’s default set of TLSv1.3 cipher suites which are TLS_AES_128_CCM_SHA256, TLS_CHACHA20_POLY1305_SHA256, TLS_AES_256_GCM_SHA384, TLS_AES_128_GCM_SHA256
Users need to aware that their clusters may be accepting TLSv1.3 connections and cipher suites when they did not expect this behavior.

[jeana-redhat]

Just a couple small formatting things and a URL fix.

[quarterpin]

Imo, based on the current discussion in the associated doc bugs for previous releases, I believe the release note title should be:
Support added for configuring TLS v1.3 ciphers via Modern Profile in the ingress operator.
This release adds Ingress operator support for TLS 1.3 ciphers that can be configured via Modern profile in tlsSecurityProfile option.

[miheer]

@quarterpin one can enable TLSv1.3 using Custom in 4.9

[skrthomas]

#33497 (RN Tracker)