INFO: Log in to your Red Hat account... INFO: Configure AWS Credentials... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com' INFO: Create ROSA with HCP cluster... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Creating cluster 'kx-106ba49528' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-106ba49528' has been created. INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information. Name: kx-106ba49528 Domain Prefix: kx-106ba49528 Display Name: kx-106ba49528 ID: 2m8gpdvpvgrh4feg358684qlt85irjor External ID: 3ab1bdd3-c667-4236-bfd4-86130a1a2e7d Control Plane: ROSA Service Hosted OpenShift Version: 4.17.42 Channel Group: stable DNS: Not ready AWS Account: 418295695583 AWS Billing Account: 418295695583 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-001fc23497e4a3aeb, subnet-00ffba09365a434bc, subnet-074cbf0329958194a, subnet-0689cd077699b690a, subnet-0f9f09e46f74cde64, subnet-033f48892ddbaa09d EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 30 2025 12:31:54 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34mnFvCKiMKSuZEn6nL5IqIaVk2 OIDC Endpoint URL: https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed) Etcd Encryption: Disabled Audit Log Forwarding: Disabled External Authentication: Disabled Zero Egress: Disabled INFO: Preparing to create operator roles. INFO: Operator Roles already exists INFO: Preparing to create OIDC Provider. INFO: OIDC provider already exists INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-106ba49528'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-106ba49528 --watch'. INFO: Track the progress of the cluster creation... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. W: Region flag will be removed from this command in future versions INFO: Cluster 'kx-106ba49528' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-106ba49528 Version 2025-10-30 12:35:35 +0000 UTC hostedclusters kx-106ba49528 ValidAWSIdentityProvider StatusUnknown 2025-10-30 12:35:36 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-30 12:35:36 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Ignition server deployment not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 HostedCluster is supported by operator configuration 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Release image is valid 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Reconciliation active on resource 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is not found 2025-10-30 12:35:39 +0000 UTC hostedclusters kx-106ba49528 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-30 12:35:39 +0000 UTC hostedclusters kx-106ba49528 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-106ba49528 Version 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Release image is valid 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Reconciliation active on resource 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Ignition server deployment not found 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0c8c27a5636c2e88b'\n\tstatus code: 400, request id: 4f247e99-c107-4791-be36-bf45be1da128"; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0c8c27a5636c2e88b'\n\tstatus code: 400, request id: 4f247e99-c107-4791-be36-bf45be1da128" 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 HostedCluster is supported by operator configuration 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the HCP 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:38 +0000 UTC hostedclusters kx-106ba49528 Condition not found in the CVO. 2025-10-30 12:35:39 +0000 UTC hostedclusters kx-106ba49528 HostedCluster is at expected version 2025-10-30 12:46:41 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-30 12:46:50 +0000 UTC hostedclusters kx-106ba49528 Configuration passes validation 2025-10-30 12:46:52 +0000 UTC hostedclusters kx-106ba49528 Required platform credentials are found 2025-10-30 12:46:55 +0000 UTC hostedclusters kx-106ba49528 Configuration passes validation 2025-10-30 12:46:55 +0000 UTC hostedclusters kx-106ba49528 lookup api.kx-106ba49528.we0x.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-30 12:46:55 +0000 UTC hostedclusters kx-106ba49528 EtcdAvailable StatefulSetNotFound 2025-10-30 12:46:55 +0000 UTC hostedclusters kx-106ba49528 AWS KMS is not configured 2025-10-30 12:46:55 +0000 UTC hostedclusters kx-106ba49528 Kube APIServer deployment not found 2025-10-30 12:46:55 +0000 UTC hostedclusters kx-106ba49528 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0c8c27a5636c2e88b'\n\tstatus code: 400, request id: 4f247e99-c107-4791-be36-bf45be1da128"; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0c8c27a5636c2e88b'\n\tstatus code: 400, request id: 4f247e99-c107-4791-be36-bf45be1da128" 2025-10-30 12:46:55 +0000 UTC hostedclusters kx-106ba49528 capi-provider deployment has 2 unavailable replicas 2025-10-30 12:46:57 +0000 UTC hostedclusters kx-106ba49528 OIDC configuration is valid 2025-10-30 12:46:57 +0000 UTC hostedclusters kx-106ba49528 Reconciliation completed successfully 2025-10-30 12:47:24 +0000 UTC hostedclusters kx-106ba49528 WebIdentityErr 2025-10-30 12:52:28 +0000 UTC hostedclusters kx-106ba49528 All is well 2025-10-30 12:52:42 +0000 UTC hostedclusters kx-106ba49528 All is well 2025-10-30 12:53:00 +0000 UTC hostedclusters kx-106ba49528 EtcdAvailable QuorumAvailable 2025-10-30 12:53:51 +0000 UTC hostedclusters kx-106ba49528 Kube APIServer deployment is available 2025-10-30 12:54:14 +0000 UTC hostedclusters kx-106ba49528 Ignition server deployment is available 2025-10-30 12:54:17 +0000 UTC hostedclusters kx-106ba49528 The hosted control plane is available INFO: Cluster 'kx-106ba49528' is now ready INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Storing login command... INFO: Check if it's able to login to OCP cluster... Retried 1 times... INFO: Check if apiserver is ready... Waiting for cluster operators to be accessible for 2m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 3m1s dns 4.17.42 False False True 3m1s DNS "default" is unavailable. image-registry False True True 2m3s Available: The deployment does not have available replicas... ingress False True True 2m45s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 2m50s kube-controller-manager 4.17.42 True False False 2m50s kube-scheduler 4.17.42 True False False 2m50s kube-storage-version-migrator monitoring network 4.17.42 True True False 2m38s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 2m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 2m50s openshift-controller-manager 4.17.42 True False False 2m50s openshift-samples operator-lifecycle-manager 4.17.42 True False False 2m52s operator-lifecycle-manager-catalog 4.17.42 True False False 2m51s operator-lifecycle-manager-packageserver 4.17.42 True False False 2m50s service-ca storage 4.17.42 False False False 2m50s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service cluster operators to be accessible finished! [INFO] Cluster operators are accessible. Waiting for cluster to be reported as healthy for 60m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 3m1s dns 4.17.42 False False True 3m1s DNS "default" is unavailable. image-registry False True True 2m3s Available: The deployment does not have available replicas... ingress False True True 2m45s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 2m50s kube-controller-manager 4.17.42 True False False 2m50s kube-scheduler 4.17.42 True False False 2m50s kube-storage-version-migrator monitoring network 4.17.42 True True False 2m38s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 2m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 2m50s openshift-controller-manager 4.17.42 True False False 2m50s openshift-samples operator-lifecycle-manager 4.17.42 True False False 2m52s operator-lifecycle-manager-catalog 4.17.42 True False False 2m51s operator-lifecycle-manager-packageserver 4.17.42 True False False 2m50s service-ca storage 4.17.42 False False False 2m50s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 4m1s dns 4.17.42 False False True 4m1s DNS "default" is unavailable. image-registry False True True 3m3s Available: The deployment does not have available replicas... ingress False True True 3m45s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 3m50s kube-controller-manager 4.17.42 True False False 3m50s kube-scheduler 4.17.42 True False False 3m50s kube-storage-version-migrator monitoring network 4.17.42 True True False 3m38s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 3m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 3m50s openshift-controller-manager 4.17.42 True False False 3m50s openshift-samples operator-lifecycle-manager 4.17.42 True False False 3m52s operator-lifecycle-manager-catalog 4.17.42 True False False 3m51s operator-lifecycle-manager-packageserver 4.17.42 True False False 3m50s service-ca storage 4.17.42 False False False 3m50s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 5m1s dns 4.17.42 False False True 5m1s DNS "default" is unavailable. image-registry False True True 4m3s Available: The deployment does not have available replicas... ingress False True True 4m45s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.17.42 True False False 9s kube-apiserver 4.17.42 True False False 4m50s kube-controller-manager 4.17.42 True False False 4m50s kube-scheduler 4.17.42 True False False 4m50s kube-storage-version-migrator 4.17.42 True False False 4s monitoring network 4.17.42 True True False 4m38s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.17.42 True False False 38s openshift-apiserver 4.17.42 True False False 4m50s openshift-controller-manager 4.17.42 True False False 4m50s openshift-samples operator-lifecycle-manager 4.17.42 True False False 4m52s operator-lifecycle-manager-catalog 4.17.42 True False False 4m51s operator-lifecycle-manager-packageserver 4.17.42 True False False 4m50s service-ca 4.17.42 True False False 6s storage 4.17.42 True False False 34s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 False True False 1s DeploymentAvailable: 0 replicas available for console deployment csi-snapshot-controller 4.17.42 True False False 6m2s dns 4.17.42 True False False 33s image-registry True True False 27s Progressing: The deployment has not completed... ingress 4.17.42 True False True 12s The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller) insights 4.17.42 True False False 70s kube-apiserver 4.17.42 True False False 5m51s kube-controller-manager 4.17.42 True False False 5m51s kube-scheduler 4.17.42 True False False 5m51s kube-storage-version-migrator 4.17.42 True False False 65s monitoring Unknown True Unknown 43s Rolling out the stack. network 4.17.42 True False False 5m39s node-tuning 4.17.42 True False False 99s openshift-apiserver 4.17.42 True False False 5m51s openshift-controller-manager 4.17.42 True False False 5m51s openshift-samples 4.17.42 True False False 26s operator-lifecycle-manager 4.17.42 True False False 5m53s operator-lifecycle-manager-catalog 4.17.42 True False False 5m52s operator-lifecycle-manager-packageserver 4.17.42 True False False 5m51s service-ca 4.17.42 True False False 67s storage 4.17.42 True False False 95s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True False False 49s csi-snapshot-controller 4.17.42 True False False 7m2s dns 4.17.42 True False False 93s image-registry 4.17.42 True False False 87s ingress 4.17.42 True False False 72s insights 4.17.42 True False False 2m10s kube-apiserver 4.17.42 True False False 6m51s kube-controller-manager 4.17.42 True False False 6m51s kube-scheduler 4.17.42 True False False 6m51s kube-storage-version-migrator 4.17.42 True False False 2m5s monitoring Unknown True Unknown 103s Rolling out the stack. network 4.17.42 True False False 6m39s node-tuning 4.17.42 True False False 2m39s openshift-apiserver 4.17.42 True False False 6m51s openshift-controller-manager 4.17.42 True False False 6m51s openshift-samples 4.17.42 True False False 86s operator-lifecycle-manager 4.17.42 True False False 6m53s operator-lifecycle-manager-catalog 4.17.42 True False False 6m52s operator-lifecycle-manager-packageserver 4.17.42 True False False 6m51s service-ca 4.17.42 True False False 2m7s storage 4.17.42 True False False 2m35s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True False False 109s csi-snapshot-controller 4.17.42 True False False 8m2s dns 4.17.42 True False False 2m33s image-registry 4.17.42 True False False 2m27s ingress 4.17.42 True False False 2m12s insights 4.17.42 True False False 3m10s kube-apiserver 4.17.42 True False False 7m51s kube-controller-manager 4.17.42 True False False 7m51s kube-scheduler 4.17.42 True False False 7m51s kube-storage-version-migrator 4.17.42 True False False 3m5s monitoring Unknown True Unknown 2m43s Rolling out the stack. network 4.17.42 True False False 7m39s node-tuning 4.17.42 True False False 3m39s openshift-apiserver 4.17.42 True False False 7m51s openshift-controller-manager 4.17.42 True False False 7m51s openshift-samples 4.17.42 True False False 2m26s operator-lifecycle-manager 4.17.42 True False False 7m53s operator-lifecycle-manager-catalog 4.17.42 True False False 7m52s operator-lifecycle-manager-packageserver 4.17.42 True False False 7m51s service-ca 4.17.42 True False False 3m7s storage 4.17.42 True False False 3m35s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True False False 2m49s csi-snapshot-controller 4.17.42 True False False 9m2s dns 4.17.42 True False False 3m33s image-registry 4.17.42 True False False 3m27s ingress 4.17.42 True False False 3m12s insights 4.17.42 True False False 4m10s kube-apiserver 4.17.42 True False False 8m51s kube-controller-manager 4.17.42 True False False 8m51s kube-scheduler 4.17.42 True False False 8m51s kube-storage-version-migrator 4.17.42 True False False 4m5s monitoring Unknown True Unknown 3m43s Rolling out the stack. network 4.17.42 True False False 8m39s node-tuning 4.17.42 True False False 4m39s openshift-apiserver 4.17.42 True False False 8m51s openshift-controller-manager 4.17.42 True False False 8m51s openshift-samples 4.17.42 True False False 3m26s operator-lifecycle-manager 4.17.42 True False False 8m53s operator-lifecycle-manager-catalog 4.17.42 True False False 8m52s operator-lifecycle-manager-packageserver 4.17.42 True False False 8m51s service-ca 4.17.42 True False False 4m7s storage 4.17.42 True False False 4m35s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True False False 3m49s csi-snapshot-controller 4.17.42 True False False 10m dns 4.17.42 True False False 4m33s image-registry 4.17.42 True False False 4m27s ingress 4.17.42 True False False 4m12s insights 4.17.42 True False False 5m10s kube-apiserver 4.17.42 True False False 9m51s kube-controller-manager 4.17.42 True False False 9m51s kube-scheduler 4.17.42 True False False 9m51s kube-storage-version-migrator 4.17.42 True False False 5m5s monitoring 4.17.42 True False False 33s network 4.17.42 True False False 9m39s node-tuning 4.17.42 True False False 5m39s openshift-apiserver 4.17.42 True False False 9m51s openshift-controller-manager 4.17.42 True False False 9m51s openshift-samples 4.17.42 True False False 4m26s operator-lifecycle-manager 4.17.42 True False False 9m53s operator-lifecycle-manager-catalog 4.17.42 True False False 9m52s operator-lifecycle-manager-packageserver 4.17.42 True False False 9m51s service-ca 4.17.42 True False False 5m7s storage 4.17.42 True False False 5m35s Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!