You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're deploying some OKD clusters in AWS on bare metal using EC2's. Is there any documentation or has anyone tested using AWS Certificate Manager for SSL certs? The AWS Load Balancer Operator fails to install.
When accessing the console the load balancer is setup but throws the usual self signed cert errors. This has the knock on affect of causing the console clusteroperator to be unavailable and is limiting both cluster upgrades and cerberus from running correctly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
We're deploying some OKD clusters in AWS on bare metal using EC2's. Is there any documentation or has anyone tested using AWS Certificate Manager for SSL certs? The AWS Load Balancer Operator fails to install.
When accessing the console the load balancer is setup but throws the usual self signed cert errors. This has the knock on affect of causing the console clusteroperator to be unavailable and is limiting both cluster upgrades and cerberus from running correctly.
oc get clusteroperator console
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.11.0-0.okd-2022-08-20-022919 False False False 151d RouteHealthAvailable: failed to GET route (https://console-openshift-console.apps.domain): Get "https://console-openshift-console.apps.domain": EOF
We can hit the console by accepting the insecure certs but the various processes like health checks fail.
Happy to provide what logs/command output in a sanitised form that people might need to support this request.
Thanks,
Paul
Beta Was this translation helpful? Give feedback.
All reactions