Bug 2105983

Summary:	Ingress VIP cannot be set when using Hypershift Agent provider
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Mario Vázquez <mavazque>
Component:	Infrastructure Operator	Assignee:	Eran Cohen <ercohen>
Status:	NEW ---	QA Contact:	Chad Crum <ccrum>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhacm-2.5	CC:	ccrum, trwest, yfirst, yobshans
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mario Vázquez 2022-07-11 12:03:16 UTC

Description of problem:

When using the agent provider for Hypershift-based deployments, there is no way to assign a specific IP for the cluster ingress.

This is an issue when using more than one worker since you don't know which nodes will host the routers, and as such, you cannot create the proper wildcard record.


Version-Release number of selected component (if applicable):
Any


How reproducible:
Always

Steps to Reproduce:
1. Create a hostedcluster
2. Scale nodepool to >= 2 replicas
3. You will get the router in one of the nodes

Actual results:

A VIP for the ingress cannot be specified.


Expected results:

A VIP for the ingress can be specified.

Additional info:

https://coreos.slack.com/archives/C01C8502FMM/p1657180562175549