apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-191-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-191.ec2.internal
      uid: 6f1617c4-4183-42d4-964e-1d0afd8ab3a3
    resourceVersion: "58185"
    uid: 60f24ff7-4f1b-49f2-bbc3-618789cf69e9
  spec:
    sourcePod: network-check-source-685456655f-lv4gt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:25:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.682µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 931.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 1.026161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:44:24Z"
    - latency: 860.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:43:24Z"
    - latency: 1.00381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:42:24Z"
    - latency: 1.513029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:41:24Z"
    - latency: 1.039418ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:40:24Z"
    - latency: 815.18µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:39:24Z"
    - latency: 829.307µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:38:24Z"
    - latency: 802.428µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:37:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-191-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-191.ec2.internal
      uid: 6f1617c4-4183-42d4-964e-1d0afd8ab3a3
    resourceVersion: "59722"
    uid: 466f65b8-a79b-4b6c-aa3e-a94fac325ed9
  spec:
    sourcePod: network-check-source-685456655f-lv4gt
    targetEndpoint: a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:24:24Z"
      message: 'load-balancer-api-external: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.971356ms
      message: 'load-balancer-api-external: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:24Z"
    - latency: 6.890766ms
      message: 'load-balancer-api-external: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:48:24Z"
    - latency: 3.399434ms
      message: 'load-balancer-api-external: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:24Z"
    - latency: 7.731692ms
      message: 'load-balancer-api-external: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:47:24Z"
    - latency: 4.560659ms
      message: 'load-balancer-api-external: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 8.604484ms
      message: 'load-balancer-api-external: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 6.145255ms
      message: 'load-balancer-api-external: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 6.780897ms
      message: 'load-balancer-api-external: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 4.899448ms
      message: 'load-balancer-api-external: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:44:24Z"
    - latency: 7.045424ms
      message: 'load-balancer-api-external: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:44:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-191-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-191.ec2.internal
      uid: 6f1617c4-4183-42d4-964e-1d0afd8ab3a3
    resourceVersion: "59721"
    uid: 11e66d10-7c1d-4fcc-82be-0c13cfe2db44
  spec:
    sourcePod: network-check-source-685456655f-lv4gt
    targetEndpoint: a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:24:24Z"
      message: 'load-balancer-api-internal: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.958849ms
      message: 'load-balancer-api-internal: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:24Z"
    - latency: 6.830591ms
      message: 'load-balancer-api-internal: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:48:24Z"
    - latency: 3.405227ms
      message: 'load-balancer-api-internal: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:24Z"
    - latency: 7.768728ms
      message: 'load-balancer-api-internal: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:47:24Z"
    - latency: 4.084245ms
      message: 'load-balancer-api-internal: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 8.682954ms
      message: 'load-balancer-api-internal: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 5.647041ms
      message: 'load-balancer-api-internal: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 6.772869ms
      message: 'load-balancer-api-internal: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 4.880085ms
      message: 'load-balancer-api-internal: tcp connection to a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:44:24Z"
    - latency: 7.029264ms
      message: 'load-balancer-api-internal: resolved host name a5be5a317ea3f447986133ee12e1eabd-dd2d478392dc670b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:44:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-191-to-network-check-target-ip-10-0-133-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-191.ec2.internal
      uid: 6f1617c4-4183-42d4-964e-1d0afd8ab3a3
    resourceVersion: "58182"
    uid: bf2e58cc-c0d7-4f42-91a2-d40643045644
  spec:
    sourcePod: network-check-source-685456655f-lv4gt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:25:24Z"
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.075µs
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 1.330818ms
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 1.681298ms
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:44:24Z"
    - latency: 921.984µs
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:43:24Z"
    - latency: 1.37343ms
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:42:24Z"
    - latency: 951.34µs
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:41:24Z"
    - latency: 883.155µs
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:40:24Z"
    - latency: 1.648148ms
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:39:24Z"
    - latency: 740.166µs
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:38:24Z"
    - latency: 1.400275ms
      message: 'network-check-target-ip-10-0-133-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:37:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-191-to-network-check-target-ip-10-0-138-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-191.ec2.internal
      uid: 6f1617c4-4183-42d4-964e-1d0afd8ab3a3
    resourceVersion: "58184"
    uid: c01ca25a-dd7f-47b3-b2df-c44e477ccbcd
  spec:
    sourcePod: network-check-source-685456655f-lv4gt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:25:24Z"
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.347401ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 2.484144ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 2.183565ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:44:24Z"
    - latency: 2.189549ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:43:24Z"
    - latency: 2.063718ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:42:24Z"
    - latency: 2.554929ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:41:24Z"
    - latency: 2.17294ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:40:24Z"
    - latency: 2.335532ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:39:24Z"
    - latency: 1.990079ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:38:24Z"
    - latency: 2.245671ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:37:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-191-to-network-check-target-ip-10-0-142-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-191.ec2.internal
      uid: 6f1617c4-4183-42d4-964e-1d0afd8ab3a3
    resourceVersion: "58183"
    uid: f3f07802-07cc-49d1-a703-0274df9ea9a1
  spec:
    sourcePod: network-check-source-685456655f-lv4gt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:25:24Z"
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.970951ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 2.212374ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 2.036781ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:44:24Z"
    - latency: 2.207055ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:43:24Z"
    - latency: 2.029601ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:42:24Z"
    - latency: 2.305508ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:41:24Z"
    - latency: 1.989602ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:40:24Z"
    - latency: 2.150188ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:39:24Z"
    - latency: 1.88963ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:38:24Z"
    - latency: 2.23724ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:37:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-191-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-191.ec2.internal
      uid: 6f1617c4-4183-42d4-964e-1d0afd8ab3a3
    resourceVersion: "59720"
    uid: f8000025-4f12-44e1-ab02-0a28535c2ff7
  spec:
    sourcePod: network-check-source-685456655f-lv4gt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:24:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:24Z"
    - latency: 1.680022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:48:24Z"
    - latency: 858.652µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:24Z"
    - latency: 1.977446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:47:24Z"
    - latency: 1.13384ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 1.885354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:46:24Z"
    - latency: 1.280418ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 1.806532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:45:24Z"
    - latency: 1.11586ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:44:24Z"
    - latency: 1.75626ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:44:24Z"
kind: List
metadata:
  resourceVersion: ""