-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.16
-
Important
-
No
-
Rejected
-
False
-
Description of problem:
Config publicIpv4Pool for cluster, but public IPs were assigned from amazon pool: aws ec2 describe-addresses --filters aws ec2 describe-addresses --filters "Name=tag:kubernetes.io/cluster/yunjiang-capool-bfqn5,Values=owned" --output json | jq -r '.Addresses[] | [.PublicIp, .PublicIpv4Pool]' [ "100.28.56.156", "amazon" ] [ "3.94.138.91", "amazon" ] [ "34.206.208.4", "amazon" ] [ "54.145.66.227", "amazon" ] [ "54.204.12.183", "amazon" ] [ "54.87.109.129", "amazon" ]
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-2024-05-08-222442
How reproducible:
Steps to Reproduce:
1.See description 2. 3.
Actual results:
See description
Expected results:
The public IPs should be assigned from custom ip pool
Additional info:
- duplicates
-
OCPBUGS-35504 Feature parity with BYO Public IPv4 terraform in CAPA
-
- Verified
-
- is blocked by
-
SPLAT-1437 [aws][BYO-IPv4] Implement BYO Public IPv4 Pool support on Installer (CAPI)
-
- Release Pending
-
- is related to
-
CORS-2890 Provision AWS with CAPI (no mgmt cluster)
-
- Testing
-