+++ This bug was initially created as a clone of Bug #1788135 +++

Description of problem:
Authentication operator is degraded causing oauth-proxies to fail

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-18-145749-ipv6.1

How reproducible:
Always

Steps to Reproduce:
1. Start an IPv6 cluster


Actual results:
Installation fails with following message:

```
DEBUG Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, console 
DEBUG Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, console 
DEBUG Still waiting for the cluster to initialize: Working towards 4.3.0-0.nightly-2019-12-18-145749-ipv6.1: 100% complete 
DEBUG Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, console 
ERROR Cluster operator authentication Degraded is True with RouteHealthDegradedFailedGet: RouteHealthDegraded: failed to GET route: net/http: TLS handshake timeout 
INFO Cluster operator authentication Progressing is Unknown with NoData:  
INFO Cluster operator authentication Available is Unknown with NoData:  
INFO Cluster operator console Progressing is True with SyncLoopRefreshProgressingInProgress: SyncLoopRefreshProgressing: Working toward version 4.3.0-0.nightly-2019-12-18-145749-ipv6.1 
INFO Cluster operator console Available is False with DeploymentAvailableInsufficientReplicas: DeploymentAvailable: 0 pods available for console deployment 
INFO Cluster operator insights Disabled is False with :  
FATAL failed to initialize the cluster: Some cluster operators are still updating: authentication, console
```


Expected results:
Installation succeeds and operator is not degraded


Additional info: