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
Copy file name to clipboardExpand all lines: docs/alb-ingress-rosa-hcp.md
+24-7Lines changed: 24 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ The use case in mind is [HyperShift hosted clusters where the Ingress capability
15
15
16
16
In order to configure an HTTPS listener on AWS ALB you need to have a certificate created in AWS Certificate Manager.
17
17
You can import an existing certificate or request a new one. Make sure the certificate is created in the same region as your cluster.
18
-
Note the certificate ARN, you will need it later.
18
+
Note the certificate ARN and the DNS name used in the certificate, you will need it later.
19
19
20
20
### Create Ingress resources for the NodePort services
21
21
@@ -73,12 +73,32 @@ EOF
73
73
### Update console config
74
74
75
75
Once the console ALBs are ready you need to let the console operator know which urls to use.
76
+
77
+
#### Add custom trusted CA (optional)
78
+
79
+
To add the CA of the certificates used in the ingress objects to [the trusted bundle of the OpenShift cluster](https://docs.openshift.com/container-platform/latest/networking/configuring-a-custom-pki.html#nw-proxy-configure-object_configuring-a-custom-pki), follow these steps:
The console ALBs have public DNS names that might not match the Subject Alternative Name (SAN) from the certificates. Ensure public DNS records matching the certificates' SANs are created and target the following hostnames:
88
+
```bash
89
+
$ oc -n openshift-console get ing console -o yaml | yq .status.loadBalancer.ingress[0].hostname
0 commit comments