ARO operator retrieves default ingress IP in wrong way
Opened this issue · 0 comments
Deleted user commented
ARO may contains many Ingress Controllers in ingressProfiles:
"ingressProfiles": [
{
"ip": "10.68.31.30",
"name": "aaa",
"visibility": "Private"
},
{
"ip": "10.68.31.254",
"name": "default",
"visibility": "Private"
},
{
"ip": "10.68.16.7",
"name": "fo-eng-eastus",
"visibility": "Private"
}
Once aro operator retrieves it, it does not check that name is "default" but just take the 1st element from list sorted alphabetically.
ARO-RP/pkg/operator/deploy/deploy.go
Line 183 in 94c46fc
It caused that CRD clusters.aro.openshift.io/v1alpha1 is wrong populated with IngressIP and it impacts ARO cluster workloads - apps accessible via default router is not reachable within ARO.
Please fix this critical bug.