Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
4.15.z
-
Low
-
No
-
Hypershift Sprint 250, Hypershift Sprint 251, Hypershift Sprint 252
-
3
-
False
-
-
There was an AWS policy issue that prevented the Cluster API Provider for AWS from retrieving the necessary domain information, which meant that installing an AWS hosted cluster with a custom domain failed.
-
Bug Fix
-
In Progress
Description
Description of problem:
AWS HyperShift clusters' nodes cannot join cluster with custom domain name in DHCP Option Set
Version-Release number of selected component (if applicable):
Any
How reproducible:
100%
Steps to Reproduce:
1. Create a VPC for a HyperShift/ROSA HCP cluster in AWS 2. Replace the VPC's DHCP Option Set with another with a custom domain name (example.com or really any domain of your choice) 3. Attempt to install a HyperShift/ROSA HCP cluster with a nodepool
Actual results:
All EC2 instances will fail to become nodes. They will generate CSR's based on the default domain name - ec2.internal for us-east-1 or ${region}.compute.internal for other regions (e.g. us-east-2.compute.internal)
Expected results:
Either that they become nodes or that we document that custom domain names in DHCP Option Sets are not allowed with HyperShift at this time. There is currently no pressing need for this feature, though customers do use this in ROSA Classic/OCP successfully.
Additional info:
This is a known gap currently in cluster-api-provider-aws (CAPA) https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/1691
Attachments
Issue Links
- blocks
-
OCPBUGS-32114 AWS HyperShift clusters' nodes cannot join cluster with custom domain name in DHCP Option Set
- Verified
- is cloned by
-
OCPBUGS-32114 AWS HyperShift clusters' nodes cannot join cluster with custom domain name in DHCP Option Set
- Verified
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update
(1 links to)