Description of problem

The "Configuring the PROXY protocol for an Ingress Controller" documentation says the following:

A cluster administrator can configure the PROXY protocol when an Ingress Controller uses either the HostNetwork or NodePortService endpoint publishing strategy types.

Since OCPBUGS-3559 was fixed in OCP 4.12.0 and backported to OCP 4.11.40 as OCPBUGS-3560, PROXY protocol can also be enabled for the Private endpoint publishing strategy type.

Version-Release number of selected component (if applicable)

4.11.40+ and 4.12+.

How reproducible

100%.

Steps to Reproduce

1. Go to https://docs.openshift.com/container-platform/4.16/networking/ingress-operator.html#nw-ingress-controller-configuration-proxy-protocol_configuring-ingress or the same part of the documentation for any other affected OpenShift version.
2. Read the first paragraph.

Actual results

The documentation states the following:

A cluster administrator can configure the PROXY protocol when an Ingress Controller uses either the HostNetwork or NodePortService endpoint publishing strategy types.

Expected results

The documentation should also that PROXY protocol can be enabled for Private:

A cluster administrator can configure the PROXY protocol when an Ingress Controller uses the HostNetwork, NodePortService, or Private endpoint publishing strategy types.

Additional info

This issue came up in a review comment for openshift/openshift-docs# 78097 to fix OCPBUGS-33700.