Deploying disconnected OCP cluster with STS
Issue
- While deploying OpenShift with STS in a disconnected mode, the image-registry operator stucks in degraded state with the following error:
- apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
...
name: image-registry
spec: {}
status:
conditions:
...
- lastTransitionTime: "2022-01-28T09:22:24Z"
message: |-
Progressing: Unable to apply resources: unable to sync storage configuration: WebIdentityErr: failed to retrieve credentials
Progressing: caused by: RequestError: send request failed
Progressing: caused by: Post "https://sts.amazonaws.com/": dial tcp x.x.x.x:443: i/o timeout
reason: Error
status: "True"
- During a disconnected OpenShift deployment, the installer fails to validate the custom endpoint for STS:
Install Config": platform.aws.serviceEndpoints[0].url: Invalid value: "https://sts.eu-region-x.amazonaws.com": dial tcp x.x.x.x:443: connect: connection timed out.
Environment
- Red Hat OpenShift Container Platform [RHOCP]
- 4.8
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.