Time Namespace Component RelatedObject Reason Message

openshift-ingress

openshift-ai-inference-openshift-ai-inference-597546666c-25bsr

Scheduled

Successfully assigned openshift-ingress/openshift-ai-inference-openshift-ai-inference-597546666c-25bsr to ip-10-0-137-189.us-west-1.compute.internal

openshift-ingress

maas-default-gateway-openshift-default-848f6bf8bc-56qxw

Scheduled

Successfully assigned openshift-ingress/maas-default-gateway-openshift-default-848f6bf8bc-56qxw to ip-10-0-137-189.us-west-1.compute.internal

openshift-ingress

kube-auth-proxy-d64f7d94f-q2g97

Scheduled

Successfully assigned openshift-ingress/kube-auth-proxy-d64f7d94f-q2g97 to ip-10-0-142-210.us-west-1.compute.internal

openshift-ingress

istiod-openshift-gateway-7ddd9cfdc8-dz2bj

Scheduled

Successfully assigned openshift-ingress/istiod-openshift-gateway-7ddd9cfdc8-dz2bj to ip-10-0-142-210.us-west-1.compute.internal

openshift-ingress

data-science-gateway-data-science-gateway-class-6bc49dd89-vmlb4

Scheduled

Successfully assigned openshift-ingress/data-science-gateway-data-science-gateway-class-6bc49dd89-vmlb4 to ip-10-0-137-189.us-west-1.compute.internal

openshift-ingress

router-default-54c95ffb47-tcxvd

FailedScheduling

no nodes available to schedule pods

openshift-ingress

router-default-54c95ffb47-tcxvd

FailedScheduling

no nodes available to schedule pods

openshift-ingress

kube-auth-proxy-d64f7d94f-7d7tb

Scheduled

Successfully assigned openshift-ingress/kube-auth-proxy-d64f7d94f-7d7tb to ip-10-0-132-247.us-west-1.compute.internal

openshift-ingress

istiod-openshift-gateway-7876bfcb74-nf542

Scheduled

Successfully assigned openshift-ingress/istiod-openshift-gateway-7876bfcb74-nf542 to ip-10-0-142-210.us-west-1.compute.internal

openshift-ingress

router-default-54c95ffb47-tcxvd

Scheduled

Successfully assigned openshift-ingress/router-default-54c95ffb47-tcxvd to ip-10-0-137-189.us-west-1.compute.internal

openshift-ingress

deployment-controller

router-default

ScalingReplicaSet

Scaled up replica set router-default-54c95ffb47 from 0 to 1

openshift-ingress

service-controller

router-default

EnsuringLoadBalancer

Ensuring load balancer

openshift-ingress

service-controller

router-default

UnAvailableLoadBalancer

There are no available nodes for LoadBalancer

openshift-ingress

service-controller

router-default

EnsuredLoadBalancer

Ensured load balancer

openshift-ingress

replicaset-controller

router-default-54c95ffb47

SuccessfulCreate

Created pod: router-default-54c95ffb47-tcxvd
(x3)

openshift-ingress

service-controller

router-default

UpdatedLoadBalancer

Updated load balancer with new hosts
(x5)

openshift-ingress

kubelet

router-default-54c95ffb47-tcxvd

FailedMount

MountVolume.SetUp failed for volume "metrics-certs" : secret "router-metrics-certs-default" not found
(x5)

openshift-ingress

kubelet

router-default-54c95ffb47-tcxvd

FailedMount

MountVolume.SetUp failed for volume "service-ca-bundle" : configmap references non-existent config key: service-ca.crt
(x2)

openshift-ingress

kubelet

router-default-54c95ffb47-tcxvd

FailedMount

MountVolume.SetUp failed for volume "metrics-certs" : secret "router-metrics-certs-default" not found
(x3)

openshift-ingress

kubelet

router-default-54c95ffb47-tcxvd

FailedMount

MountVolume.SetUp failed for volume "service-ca-bundle" : configmap references non-existent config key: service-ca.crt

openshift-ingress

kubelet

router-default-54c95ffb47-tcxvd

Started

Container started

openshift-ingress

multus

router-default-54c95ffb47-tcxvd

AddedInterface

Add eth0 [10.132.0.16/23] from ovn-kubernetes

openshift-ingress

kubelet

router-default-54c95ffb47-tcxvd

Pulled

Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e" already present on machine and can be accessed by the pod

openshift-ingress

kubelet

router-default-54c95ffb47-tcxvd

Created

Container created

openshift-ingress

gateway_labeler_controller

maas-default-gateway

AddedLabel

Added label istio.io/rev=openshift-gateway to gateway maas-default-gateway

openshift-ingress

replicaset-controller

istiod-openshift-gateway-7876bfcb74

SuccessfulCreate

Created pod: istiod-openshift-gateway-7876bfcb74-nf542

openshift-ingress

multus

istiod-openshift-gateway-7876bfcb74-nf542

AddedInterface

Add eth0 [10.133.0.20/23] from ovn-kubernetes

openshift-ingress

deployment-controller

istiod-openshift-gateway

ScalingReplicaSet

Scaled up replica set istiod-openshift-gateway-7876bfcb74 from 0 to 1

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-nf542

Pulling

Pulling image "registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9@sha256:d5adf3101d4e14c710cd05afb3fa53498e3c5fb31a120f1bb007fba2e3b376f8"

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-nf542

Created

Container created

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-nf542

Pulled

Successfully pulled image "registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9@sha256:d5adf3101d4e14c710cd05afb3fa53498e3c5fb31a120f1bb007fba2e3b376f8" in 3.905s (3.905s including waiting). Image size: 185476477 bytes.

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-nf542

Started

Container started

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-nf542

Unhealthy

Readiness probe failed: HTTP probe failed with statuscode: 503

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-nf542

ProbeError

Readiness probe error: HTTP probe failed with statuscode: 503 body:

openshift-ingress

replicaset-controller

maas-default-gateway-openshift-default-848f6bf8bc

SuccessfulCreate

Created pod: maas-default-gateway-openshift-default-848f6bf8bc-56qxw

openshift-ingress

service-controller

openshift-ai-inference-openshift-ai-inference

EnsuringLoadBalancer

Ensuring load balancer

openshift-ingress

deployment-controller

maas-default-gateway-openshift-default

ScalingReplicaSet

Scaled up replica set maas-default-gateway-openshift-default-848f6bf8bc from 0 to 1

openshift-ingress

replicaset-controller

openshift-ai-inference-openshift-ai-inference-597546666c

SuccessfulCreate

Created pod: openshift-ai-inference-openshift-ai-inference-597546666c-25bsr

openshift-ingress

deployment-controller

openshift-ai-inference-openshift-ai-inference

ScalingReplicaSet

Scaled up replica set openshift-ai-inference-openshift-ai-inference-597546666c from 0 to 1

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-597546666c-25bsr

Pulling

Pulling image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55"

openshift-ingress

multus

openshift-ai-inference-openshift-ai-inference-597546666c-25bsr

AddedInterface

Add eth0 [10.132.0.34/23] from ovn-kubernetes

openshift-ingress

multus

maas-default-gateway-openshift-default-848f6bf8bc-56qxw

AddedInterface

Add eth0 [10.132.0.33/23] from ovn-kubernetes

openshift-ingress

kubelet

maas-default-gateway-openshift-default-848f6bf8bc-56qxw

Pulling

Pulling image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55"

openshift-ingress

service-controller

openshift-ai-inference-openshift-ai-inference

EnsuredLoadBalancer

Ensured load balancer

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-597546666c-25bsr

Created

Container created

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-597546666c-25bsr

Pulled

Successfully pulled image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55" in 9.847s (9.847s including waiting). Image size: 183555333 bytes.

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-597546666c-25bsr

Started

Container started

openshift-ingress

kubelet

maas-default-gateway-openshift-default-848f6bf8bc-56qxw

Created

Container created

openshift-ingress

kubelet

maas-default-gateway-openshift-default-848f6bf8bc-56qxw

Pulled

Successfully pulled image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55" in 12.389s (12.389s including waiting). Image size: 183555333 bytes.

openshift-ingress

kubelet

maas-default-gateway-openshift-default-848f6bf8bc-56qxw

Started

Container started
(x3)

openshift-ingress

horizontal-pod-autoscaler

maas-default-gateway-openshift-default

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x3)

openshift-ingress

horizontal-pod-autoscaler

openshift-ai-inference-openshift-ai-inference

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x3)

openshift-ingress

horizontal-pod-autoscaler

maas-default-gateway-openshift-default

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x3)

openshift-ingress

horizontal-pod-autoscaler

openshift-ai-inference-openshift-ai-inference

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

replicaset-controller

kube-auth-proxy-d64f7d94f

SuccessfulCreate

Created pod: kube-auth-proxy-d64f7d94f-q2g97

openshift-ingress

deployment-controller

data-science-gateway-data-science-gateway-class

ScalingReplicaSet

Scaled up replica set data-science-gateway-data-science-gateway-class-6bc49dd89 from 0 to 1

openshift-ingress

deployment-controller

kube-auth-proxy

ScalingReplicaSet

Scaled up replica set kube-auth-proxy-d64f7d94f from 0 to 2

openshift-ingress

replicaset-controller

kube-auth-proxy-d64f7d94f

SuccessfulCreate

Created pod: kube-auth-proxy-d64f7d94f-7d7tb

openshift-ingress

replicaset-controller

data-science-gateway-data-science-gateway-class-6bc49dd89

SuccessfulCreate

Created pod: data-science-gateway-data-science-gateway-class-6bc49dd89-vmlb4

openshift-ingress

multus

kube-auth-proxy-d64f7d94f-q2g97

AddedInterface

Add eth0 [10.133.0.22/23] from ovn-kubernetes

openshift-ingress

multus

kube-auth-proxy-d64f7d94f-7d7tb

AddedInterface

Add eth0 [10.134.0.24/23] from ovn-kubernetes

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-7d7tb

Pulling

Pulling image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035"

openshift-ingress

kubelet

data-science-gateway-data-science-gateway-class-6bc49dd89-vmlb4

Started

Container started

openshift-ingress

kubelet

data-science-gateway-data-science-gateway-class-6bc49dd89-vmlb4

Created

Container created

openshift-ingress

kubelet

data-science-gateway-data-science-gateway-class-6bc49dd89-vmlb4

Pulled

Container image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55" already present on machine and can be accessed by the pod

openshift-ingress

multus

data-science-gateway-data-science-gateway-class-6bc49dd89-vmlb4

AddedInterface

Add eth0 [10.132.0.42/23] from ovn-kubernetes

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-q2g97

Pulling

Pulling image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035"

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-q2g97

Pulled

Successfully pulled image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035" in 2.942s (2.942s including waiting). Image size: 188904677 bytes.

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-q2g97

Started

Container started

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-7d7tb

Created

Container created

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-7d7tb

Started

Container started

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-q2g97

Created

Container created

openshift-ingress

kubelet

kube-auth-proxy-d64f7d94f-7d7tb

Pulled

Successfully pulled image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035" in 2.999s (2.999s including waiting). Image size: 188904677 bytes.

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedGetResourceMetric

failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)
(x3)

openshift-ingress

horizontal-pod-autoscaler

data-science-gateway-data-science-gateway-class

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x3)

openshift-ingress

horizontal-pod-autoscaler

data-science-gateway-data-science-gateway-class

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

replicaset-controller

istiod-openshift-gateway-7ddd9cfdc8

SuccessfulCreate

Created pod: istiod-openshift-gateway-7ddd9cfdc8-dz2bj

openshift-ingress

deployment-controller

istiod-openshift-gateway

ScalingReplicaSet

Scaled up replica set istiod-openshift-gateway-7ddd9cfdc8 from 0 to 1

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-dz2bj

Pulled

Container image "registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9@sha256:d5adf3101d4e14c710cd05afb3fa53498e3c5fb31a120f1bb007fba2e3b376f8" already present on machine and can be accessed by the pod

openshift-ingress

multus

istiod-openshift-gateway-7ddd9cfdc8-dz2bj

AddedInterface

Add eth0 [10.133.0.23/23] from ovn-kubernetes

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-dz2bj

Created

Container created

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-dz2bj

Started

Container started

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-dz2bj

ProbeError

Readiness probe error: HTTP probe failed with statuscode: 503 body:

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-dz2bj

Unhealthy

Readiness probe failed: HTTP probe failed with statuscode: 503

openshift-ingress

replicaset-controller

istiod-openshift-gateway-7876bfcb74

SuccessfulDelete

Deleted pod: istiod-openshift-gateway-7876bfcb74-nf542

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-nf542

Killing

Stopping container discovery

openshift-ingress

deployment-controller

istiod-openshift-gateway

ScalingReplicaSet

Scaled down replica set istiod-openshift-gateway-7876bfcb74 from 1 to 0
(x5)

openshift-ingress

horizontal-pod-autoscaler

istiod-openshift-gateway

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x5)

openshift-ingress

horizontal-pod-autoscaler

istiod-openshift-gateway

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API