-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.14.0
-
None
-
Important
-
No
-
3
-
Sprint 240
-
1
-
Rejected
-
False
-
Description of problem:
Error from server (InternalError): error when creating "awslb/ingress-test.yaml": Internal error occurred: failed calling webhook "vingress.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-controller-cluster.aws-load-balancer-operator.svc:9443/validate-networking-v1-ingress?timeout=10s": remote error: tls: protocol version not supported
Version-Release number of selected component (if applicable):
OCP: 4.14.0-0.nightly-2023-06-11-212615 ALBO: 1.0.0
How reproducible:
100%
Steps to Reproduce:
1. fresh install 4.14 cluster with FIPS enabled 2. create AWS Load Balancer operator 3. create ALB controller (operand) 4. create a tested ingress resource
Actual results:
remote error: tls: protocol version not supported
Expected results:
the ingress resource should be created and LB should be provisioned
Additional info:
no this issue in non-FIPS cluster
- is duplicated by
-
OCPBUGS-17201 AWS Load Balancer Operator (ALBO) does not support FIPS enabled clusters
- Closed
- links to
-
RHEA-2023:123015 Release of AWS Load Balancer Operator on OperatorHub
- mentioned on
(2 mentioned on)