apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T01:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: e43d4781-dfdb-4a14-ad1c-6ffce9de176d
    resourceVersion: "199148"
    uid: ff8a9293-5ff0-46ba-922a-717cc8e6e5af
  spec:
    sourcePod: network-check-source-6f78d59f99-jqlwc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T01:37:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.336686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:08:33Z"
    - latency: 1.029661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:07:33Z"
    - latency: 10.765545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 9.529184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 3.020015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 1.263615ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 987.827µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:02:33Z"
    - latency: 1.132616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:01:33Z"
    - latency: 5.783062ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:00:33Z"
    - latency: 4.454616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T02:59:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T01:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: e43d4781-dfdb-4a14-ad1c-6ffce9de176d
    resourceVersion: "197560"
    uid: e10bb285-4f5e-4c09-a7d8-efad52c74ce4
  spec:
    sourcePod: network-check-source-6f78d59f99-jqlwc
    targetEndpoint: a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T01:36:33Z"
      message: 'load-balancer-api-external: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 42.53095ms
      message: 'load-balancer-api-external: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 51.536221ms
      message: 'load-balancer-api-external: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 28.176478ms
      message: 'load-balancer-api-external: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 51.280003ms
      message: 'load-balancer-api-external: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 18.084307ms
      message: 'load-balancer-api-external: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 12.1899ms
      message: 'load-balancer-api-external: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 16.231343ms
      message: 'load-balancer-api-external: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 6.784821ms
      message: 'load-balancer-api-external: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 16.251334ms
      message: 'load-balancer-api-external: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:02:33Z"
    - latency: 7.057718ms
      message: 'load-balancer-api-external: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:02:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T01:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: e43d4781-dfdb-4a14-ad1c-6ffce9de176d
    resourceVersion: "197562"
    uid: b9998ad9-cc34-46ca-9b0b-ed30aa21e68f
  spec:
    sourcePod: network-check-source-6f78d59f99-jqlwc
    targetEndpoint: a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T01:36:33Z"
      message: 'load-balancer-api-internal: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 43.084407ms
      message: 'load-balancer-api-internal: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 53.363894ms
      message: 'load-balancer-api-internal: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 27.014572ms
      message: 'load-balancer-api-internal: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 55.717594ms
      message: 'load-balancer-api-internal: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 19.610149ms
      message: 'load-balancer-api-internal: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 11.955309ms
      message: 'load-balancer-api-internal: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 17.487187ms
      message: 'load-balancer-api-internal: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 6.840743ms
      message: 'load-balancer-api-internal: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 16.916899ms
      message: 'load-balancer-api-internal: tcp connection to a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:02:33Z"
    - latency: 6.972011ms
      message: 'load-balancer-api-internal: resolved host name a2616d5a360074f9b9a340f4a69dd658-dfef6ee71109def2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:02:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T01:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-ip-10-0-130-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: e43d4781-dfdb-4a14-ad1c-6ffce9de176d
    resourceVersion: "199146"
    uid: 348fb2cb-6029-4db1-874a-b2175182ac35
  spec:
    sourcePod: network-check-source-6f78d59f99-jqlwc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T01:37:33Z"
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205251ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:08:33Z"
    - latency: 2.279893ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:07:33Z"
    - latency: 11.239527ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 6.261597ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 4.248699ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 2.305067ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 2.151434ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:02:33Z"
    - latency: 2.262579ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:01:33Z"
    - latency: 10.004763ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:00:33Z"
    - latency: 5.865843ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T02:59:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T01:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-ip-10-0-142-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: e43d4781-dfdb-4a14-ad1c-6ffce9de176d
    resourceVersion: "199145"
    uid: 03ed545b-4e35-4486-93dd-84c1c7a2f0a3
  spec:
    sourcePod: network-check-source-6f78d59f99-jqlwc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T01:37:33Z"
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 759.175µs
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:08:33Z"
    - latency: 1.196272ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:07:33Z"
    - latency: 11.581739ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 6.190438ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 2.961343ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 952.341µs
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 773.141µs
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:02:33Z"
    - latency: 1.070591ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:01:33Z"
    - latency: 2.879152ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:00:33Z"
    - latency: 12.363049ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T02:59:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T01:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-ip-10-0-143-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: e43d4781-dfdb-4a14-ad1c-6ffce9de176d
    resourceVersion: "199147"
    uid: 429f256e-1e97-4e42-ba21-6772a807408b
  spec:
    sourcePod: network-check-source-6f78d59f99-jqlwc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T01:37:33Z"
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.374922ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:08:33Z"
    - latency: 2.470954ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:07:33Z"
    - latency: 11.594759ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 6.835074ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 4.394597ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 2.644379ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 2.225153ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:02:33Z"
    - latency: 2.46983ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:01:33Z"
    - latency: 10.747706ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:00:33Z"
    - latency: 3.880207ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T02:59:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T01:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: e43d4781-dfdb-4a14-ad1c-6ffce9de176d
    resourceVersion: "197558"
    uid: 9e7b420a-6e2d-48f4-84f8-2092d67725fd
  spec:
    sourcePod: network-check-source-6f78d59f99-jqlwc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T01:36:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.811049ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 29.97661ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:06:33Z"
    - latency: 7.636587ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 9.928492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:05:33Z"
    - latency: 1.503382ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 4.83264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:04:33Z"
    - latency: 882.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 1.867723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:03:33Z"
    - latency: 964.321µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:02:33Z"
    - latency: 2.518018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:02:33Z"
kind: List
metadata:
  resourceVersion: ""