Hide Forgot
Platform: Azure Stack Hub IPI & UPI Azure Stack Hub does not add the additionalTrustBundle to the cloud provider config or the bootstrap ignition stub, so this does not allow for installation in environments that need certificates signed by internal CAs. Our new environment Azure Stack environment, WWT, uses certificates signed by internal CAs so we see that installations fail there. First, installations fail when trying to pull ignition from the storage blob. This can be handled in the UPI instructions. Second, installations fail when operators do not have the trust bundle. The installer needs to place the additional trust bundle in the cloud provider config, then we need to follow up with operators to make sure they are using it. The operators we know we need to follow up with are: CCM (cloud team and machine-api for 4.10 only) image registry storage network edge for ingress controller
Confirmed we can now handle the self-signed certificate our ASH instance uses for cluster installation. Once the bootstrap ignition is updated to include the cert the bootstrap node will then download necessary content for installation and the cluster will use it without issues.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056