apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-251-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-251.ec2.internal
      uid: ec0c9aff-5c22-4d52-85c7-ea04e082f888
    resourceVersion: "158511"
    uid: ecff8b91-843a-41b4-9df3-bba0e7cf7aba
  spec:
    sourcePod: network-check-source-6f78d59f99-glvhs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:02:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.339134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 4.594719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 1.278452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:31Z"
    - latency: 1.414227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:31Z"
    - latency: 1.440747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:31Z"
    - latency: 1.075827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:31Z"
    - latency: 1.213117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:31Z"
    - latency: 7.997884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:31Z"
    - latency: 2.081995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:31Z"
    - latency: 1.774764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-251-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-251.ec2.internal
      uid: ec0c9aff-5c22-4d52-85c7-ea04e082f888
    resourceVersion: "163946"
    uid: 254dcd48-6c99-417b-b9ca-03e749089ca9
  spec:
    sourcePod: network-check-source-6f78d59f99-glvhs
    targetEndpoint: ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:01:31Z"
      message: 'load-balancer-api-external: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.134635ms
      message: 'load-balancer-api-external: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:07:31Z"
    - latency: 8.440053ms
      message: 'load-balancer-api-external: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:07:31Z"
    - latency: 17.928267ms
      message: 'load-balancer-api-external: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:06:31Z"
    - latency: 11.01243ms
      message: 'load-balancer-api-external: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:06:31Z"
    - latency: 20.298266ms
      message: 'load-balancer-api-external: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 8.460712ms
      message: 'load-balancer-api-external: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 23.127669ms
      message: 'load-balancer-api-external: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 81.938249ms
      message: 'load-balancer-api-external: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 54.532207ms
      message: 'load-balancer-api-external: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:31Z"
    - latency: 7.81709ms
      message: 'load-balancer-api-external: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:03:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-251-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-251.ec2.internal
      uid: ec0c9aff-5c22-4d52-85c7-ea04e082f888
    resourceVersion: "163945"
    uid: c9ce2bb6-95ed-4a8e-a8ac-9a32282fbd5f
  spec:
    sourcePod: network-check-source-6f78d59f99-glvhs
    targetEndpoint: ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:01:31Z"
      message: 'load-balancer-api-internal: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.181602ms
      message: 'load-balancer-api-internal: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:07:31Z"
    - latency: 8.440083ms
      message: 'load-balancer-api-internal: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:07:31Z"
    - latency: 16.013556ms
      message: 'load-balancer-api-internal: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:06:31Z"
    - latency: 10.859359ms
      message: 'load-balancer-api-internal: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:06:31Z"
    - latency: 20.658225ms
      message: 'load-balancer-api-internal: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 8.399553ms
      message: 'load-balancer-api-internal: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 40.504851ms
      message: 'load-balancer-api-internal: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 81.404397ms
      message: 'load-balancer-api-internal: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 26.073439ms
      message: 'load-balancer-api-internal: tcp connection to ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:31Z"
    - latency: 7.63565ms
      message: 'load-balancer-api-internal: resolved host name ab201029ee7e2438cae25c69ded34c55-2c29b25c9fc974f3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:03:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-251-to-network-check-target-ip-10-0-131-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-251.ec2.internal
      uid: ec0c9aff-5c22-4d52-85c7-ea04e082f888
    resourceVersion: "158509"
    uid: ae9456d4-0c53-4c9b-84bc-f98dd7d4eba8
  spec:
    sourcePod: network-check-source-6f78d59f99-glvhs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:02:31Z"
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.212244ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 46.349506ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 2.344752ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:31Z"
    - latency: 3.041778ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:31Z"
    - latency: 2.682358ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:31Z"
    - latency: 2.97926ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:31Z"
    - latency: 2.760563ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:31Z"
    - latency: 9.962839ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:31Z"
    - latency: 2.685623ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:31Z"
    - latency: 2.103798ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-251-to-network-check-target-ip-10-0-138-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-251.ec2.internal
      uid: ec0c9aff-5c22-4d52-85c7-ea04e082f888
    resourceVersion: "158508"
    uid: 87855ab3-1aae-4b00-aae8-d5edb5fbf633
  spec:
    sourcePod: network-check-source-6f78d59f99-glvhs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:02:31Z"
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.400531ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 50.474372ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 2.03071ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:31Z"
    - latency: 2.046167ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:31Z"
    - latency: 2.876932ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:31Z"
    - latency: 2.871159ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:31Z"
    - latency: 2.455156ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:31Z"
    - latency: 7.684606ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:31Z"
    - latency: 2.048593ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:31Z"
    - latency: 3.091394ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-251-to-network-check-target-ip-10-0-141-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-251.ec2.internal
      uid: ec0c9aff-5c22-4d52-85c7-ea04e082f888
    resourceVersion: "158507"
    uid: d96394cb-9ca0-4fb7-8bc2-ecacf22e285a
  spec:
    sourcePod: network-check-source-6f78d59f99-glvhs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:02:31Z"
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.244944ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 5.508194ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 1.501935ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:31Z"
    - latency: 1.071857ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:31Z"
    - latency: 1.114115ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:31Z"
    - latency: 1.537702ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:31Z"
    - latency: 1.895591ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:31Z"
    - latency: 9.447014ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:31Z"
    - latency: 2.147106ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:31Z"
    - latency: 1.092146ms
      message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-251-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-251.ec2.internal
      uid: ec0c9aff-5c22-4d52-85c7-ea04e082f888
    resourceVersion: "163942"
    uid: edf28bc3-fce8-4003-ae4b-1d467274021a
  spec:
    sourcePod: network-check-source-6f78d59f99-glvhs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:01:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029152ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:07:31Z"
    - latency: 2.26079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:07:31Z"
    - latency: 1.070282ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:06:31Z"
    - latency: 3.117806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:06:31Z"
    - latency: 1.152132ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 2.487421ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:05:31Z"
    - latency: 2.59246ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 50.848813ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:04:31Z"
    - latency: 1.091446ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:31Z"
    - latency: 2.759143ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:03:31Z"
kind: List
metadata:
  resourceVersion: ""