private-router network policy breaks ignition access for 4.13.z OCP clusters

In 4.13.z releases, the request-serving label is not present in the ignition-server-proxy deployment. The network policy in place prevents egress from the private router to pods that do not have the label, resulting in the ignition-server endpoint not being available from the outside. 

4.13.12 OCP, 4.14 HO

Always

1. Install latest HO
2. Create a HostedCluster with version 4.13.12
3. Wait for nodes to join

Nodes never join

Nodes join

Nodes are not joining because of the blocked egress from the router to the ignition-server-proxy