Bug 2105983 - Ingress VIP cannot be set when using Hypershift Agent provider
Summary: Ingress VIP cannot be set when using Hypershift Agent provider
Keywords:
Status: NEW
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Infrastructure Operator
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Eran Cohen
QA Contact: Chad Crum
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-11 12:03 UTC by Mario Vázquez
Modified: 2023-10-19 05:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 24290 0 None None None 2022-07-14 17:41:46 UTC
Red Hat Issue Tracker MGMTBUGSM-469 0 None None None 2022-07-14 14:14:12 UTC

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
Note You need to log in before you can comment on or make changes to this bug.