apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:34:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 88e3a2d3-35bc-4ac0-bfa1-bc37e8732d29
    resourceVersion: "26223"
    uid: 65cefaf4-847f-412e-9f27-4841d8df8056
  spec:
    sourcePod: network-check-source-989f8b8dc-x7sdl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T17:41:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:48:43Z"
    - latency: 1.033757ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:47:43Z"
    - latency: 899.322µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 904.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 1.095778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 1.107007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 1.036923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:42:43Z"
    - latency: 948.728µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:41:43Z"
    - latency: 1.085869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:40:43Z"
    - latency: 1.141957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:39:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:34:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 88e3a2d3-35bc-4ac0-bfa1-bc37e8732d29
    resourceVersion: "25017"
    uid: 90b5e197-b506-42ef-9506-551f2367303a
  spec:
    sourcePod: network-check-source-989f8b8dc-x7sdl
    targetEndpoint: af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T17:40:43Z"
      message: 'load-balancer-api-external: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.621238ms
      message: 'load-balancer-api-external: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 8.477028ms
      message: 'load-balancer-api-external: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 3.664145ms
      message: 'load-balancer-api-external: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 8.522365ms
      message: 'load-balancer-api-external: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 4.758832ms
      message: 'load-balancer-api-external: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 8.963742ms
      message: 'load-balancer-api-external: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 5.21215ms
      message: 'load-balancer-api-external: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 7.965112ms
      message: 'load-balancer-api-external: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 8.830938ms
      message: 'load-balancer-api-external: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:42:43Z"
    - latency: 8.524988ms
      message: 'load-balancer-api-external: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:42:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:34:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 88e3a2d3-35bc-4ac0-bfa1-bc37e8732d29
    resourceVersion: "25016"
    uid: 2cdde7f4-9aab-4ea2-991e-d596a85c133a
  spec:
    sourcePod: network-check-source-989f8b8dc-x7sdl
    targetEndpoint: af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T17:40:43Z"
      message: 'load-balancer-api-internal: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.696055ms
      message: 'load-balancer-api-internal: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 8.38766ms
      message: 'load-balancer-api-internal: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 5.255174ms
      message: 'load-balancer-api-internal: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 8.45469ms
      message: 'load-balancer-api-internal: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 4.771969ms
      message: 'load-balancer-api-internal: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 8.89226ms
      message: 'load-balancer-api-internal: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 5.970957ms
      message: 'load-balancer-api-internal: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 8.019746ms
      message: 'load-balancer-api-internal: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 8.859845ms
      message: 'load-balancer-api-internal: tcp connection to af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:42:43Z"
    - latency: 8.447654ms
      message: 'load-balancer-api-internal: resolved host name af7fa56bb7a7343059b83c8fbfd2eb6d-791c980d36df145e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:42:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:34:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-ip-10-0-139-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 88e3a2d3-35bc-4ac0-bfa1-bc37e8732d29
    resourceVersion: "26221"
    uid: b3a061d0-6496-4b16-a44a-cde2b4e3f538
  spec:
    sourcePod: network-check-source-989f8b8dc-x7sdl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T17:41:43Z"
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.065547ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:48:43Z"
    - latency: 2.144461ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:47:43Z"
    - latency: 2.055827ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 1.971502ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 2.038169ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 2.273425ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 2.298905ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:42:43Z"
    - latency: 2.213693ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:41:43Z"
    - latency: 2.343663ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:40:43Z"
    - latency: 2.139532ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:39:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:34:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-ip-10-0-139-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 88e3a2d3-35bc-4ac0-bfa1-bc37e8732d29
    resourceVersion: "26222"
    uid: 0df45d79-5e05-4317-8c3d-c5bfa95faad2
  spec:
    sourcePod: network-check-source-989f8b8dc-x7sdl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T17:41:43Z"
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.71737ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:48:43Z"
    - latency: 1.994214ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:47:43Z"
    - latency: 1.64879ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 1.906895ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 1.471988ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 1.829341ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 1.682071ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:42:43Z"
    - latency: 1.834817ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:41:43Z"
    - latency: 1.695256ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:40:43Z"
    - latency: 1.845821ms
      message: 'network-check-target-ip-10-0-139-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:39:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:34:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-ip-10-0-142-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 88e3a2d3-35bc-4ac0-bfa1-bc37e8732d29
    resourceVersion: "26220"
    uid: 21e3ca9c-247d-487d-974f-69a814beb0a1
  spec:
    sourcePod: network-check-source-989f8b8dc-x7sdl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T17:41:43Z"
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.859µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:48:43Z"
    - latency: 744.205µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:47:43Z"
    - latency: 913.865µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 910.727µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 778.725µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 1.47624ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 850.393µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:42:43Z"
    - latency: 1.083901ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:41:43Z"
    - latency: 934.733µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:40:43Z"
    - latency: 944.884µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:39:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:34:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 88e3a2d3-35bc-4ac0-bfa1-bc37e8732d29
    resourceVersion: "25015"
    uid: 903f0115-d23f-4f00-a5c3-cea0d73eecbb
  spec:
    sourcePod: network-check-source-989f8b8dc-x7sdl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T17:40:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 827.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 1.72264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:46:43Z"
    - latency: 839.286µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 1.618938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:45:43Z"
    - latency: 958.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 1.871744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:44:43Z"
    - latency: 920.054µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 1.768524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:43:43Z"
    - latency: 976.933µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:42:43Z"
    - latency: 1.880337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:42:43Z"
kind: List
metadata:
  resourceVersion: ""