apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:30:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-24-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-24.ec2.internal
      uid: 034acca0-3872-4c70-b061-87b63923494b
    resourceVersion: "54061"
    uid: b45f6518-939b-4dcc-a9ca-780a7333cad4
  spec:
    sourcePod: network-check-source-685456655f-z9gtc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:37:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.113475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 847.561µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 1.244079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:54Z"
    - latency: 935.266µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:54Z"
    - latency: 1.077006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:54Z"
    - latency: 1.127443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:54Z"
    - latency: 1.21432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:54Z"
    - latency: 1.812864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:54Z"
    - latency: 1.49429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:54Z"
    - latency: 1.029759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:30:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-24-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-24.ec2.internal
      uid: 034acca0-3872-4c70-b061-87b63923494b
    resourceVersion: "55801"
    uid: 8b20db61-8853-4d6e-a087-a56b9c3c5e89
  spec:
    sourcePod: network-check-source-685456655f-z9gtc
    targetEndpoint: a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:36:54Z"
      message: 'load-balancer-api-external: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.845231ms
      message: 'load-balancer-api-external: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T07:00:54Z"
    - latency: 8.934211ms
      message: 'load-balancer-api-external: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T07:00:54Z"
    - latency: 6.468979ms
      message: 'load-balancer-api-external: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:59:54Z"
    - latency: 8.12312ms
      message: 'load-balancer-api-external: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:59:54Z"
    - latency: 5.18861ms
      message: 'load-balancer-api-external: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 8.283575ms
      message: 'load-balancer-api-external: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 3.647044ms
      message: 'load-balancer-api-external: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 7.982918ms
      message: 'load-balancer-api-external: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 4.580343ms
      message: 'load-balancer-api-external: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:54Z"
    - latency: 8.150667ms
      message: 'load-balancer-api-external: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:56:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:30:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-24-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-24.ec2.internal
      uid: 034acca0-3872-4c70-b061-87b63923494b
    resourceVersion: "55800"
    uid: 6fb33424-d69c-4d88-b043-2c8fa0eeb129
  spec:
    sourcePod: network-check-source-685456655f-z9gtc
    targetEndpoint: a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:36:54Z"
      message: 'load-balancer-api-internal: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.808223ms
      message: 'load-balancer-api-internal: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T07:00:54Z"
    - latency: 8.997626ms
      message: 'load-balancer-api-internal: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T07:00:54Z"
    - latency: 6.456645ms
      message: 'load-balancer-api-internal: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:59:54Z"
    - latency: 8.172596ms
      message: 'load-balancer-api-internal: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:59:54Z"
    - latency: 5.199389ms
      message: 'load-balancer-api-internal: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 8.258319ms
      message: 'load-balancer-api-internal: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 4.152901ms
      message: 'load-balancer-api-internal: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 8.012684ms
      message: 'load-balancer-api-internal: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 4.540906ms
      message: 'load-balancer-api-internal: tcp connection to a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:54Z"
    - latency: 8.182635ms
      message: 'load-balancer-api-internal: resolved host name a60009d6da40b4cdea426d8dc4f3085d-c713fb59762ed787.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:56:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:30:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-24-to-network-check-target-ip-10-0-137-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-24.ec2.internal
      uid: 034acca0-3872-4c70-b061-87b63923494b
    resourceVersion: "54060"
    uid: f6df49eb-6dbc-471f-95b2-7bf81563ad24
  spec:
    sourcePod: network-check-source-685456655f-z9gtc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:37:54Z"
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.332474ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 2.388625ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 2.334261ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:54Z"
    - latency: 2.197575ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:54Z"
    - latency: 2.394949ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:54Z"
    - latency: 2.17284ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:54Z"
    - latency: 2.344696ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:54Z"
    - latency: 2.30887ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:54Z"
    - latency: 1.960762ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:54Z"
    - latency: 2.247361ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:30:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-24-to-network-check-target-ip-10-0-141-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-24.ec2.internal
      uid: 034acca0-3872-4c70-b061-87b63923494b
    resourceVersion: "54059"
    uid: 25685fad-41e3-47f7-ba51-ec5591a1a019
  spec:
    sourcePod: network-check-source-685456655f-z9gtc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:37:54Z"
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.853001ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 1.968872ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 2.123653ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:54Z"
    - latency: 2.059963ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:54Z"
    - latency: 2.09436ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:54Z"
    - latency: 2.003906ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:54Z"
    - latency: 2.058653ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:54Z"
    - latency: 2.006965ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:54Z"
    - latency: 2.112468ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:54Z"
    - latency: 2.143394ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:30:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-24-to-network-check-target-ip-10-0-142-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-24.ec2.internal
      uid: 034acca0-3872-4c70-b061-87b63923494b
    resourceVersion: "54058"
    uid: 0c04907b-6ca5-47e3-a4c8-66fb785f4cd0
  spec:
    sourcePod: network-check-source-685456655f-z9gtc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:37:54Z"
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.239µs
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 937.647µs
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 991.124µs
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:54Z"
    - latency: 1.253695ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:54Z"
    - latency: 1.440385ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:54Z"
    - latency: 957.125µs
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:54Z"
    - latency: 972.674µs
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:54Z"
    - latency: 866.919µs
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:54Z"
    - latency: 957.299µs
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:54Z"
    - latency: 1.298328ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:30:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-24-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-24.ec2.internal
      uid: 034acca0-3872-4c70-b061-87b63923494b
    resourceVersion: "55799"
    uid: faba9a2f-1d8d-48ee-ab5f-8ff750f4b944
  spec:
    sourcePod: network-check-source-685456655f-z9gtc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:36:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.56µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T07:00:54Z"
    - latency: 2.455154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T07:00:54Z"
    - latency: 990.563µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:59:54Z"
    - latency: 2.090026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:59:54Z"
    - latency: 958.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 1.635681ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:58:54Z"
    - latency: 1.06164ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 1.653559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:57:54Z"
    - latency: 851.597µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:54Z"
    - latency: 1.757695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:56:54Z"
kind: List
metadata:
  resourceVersion: ""