apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T12:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.ec2.internal
      uid: 3693b7eb-b829-4a90-be42-bf466d015ebf
    resourceVersion: "25732"
    uid: ff671927-6611-4b97-aad6-52486e9168dc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6p7pz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T12:40:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 993.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 1.326569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 1.121849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 903.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:05:24Z"
    - latency: 1.518085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:04:24Z"
    - latency: 1.090129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:03:24Z"
    - latency: 1.084232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:02:24Z"
    - latency: 1.008722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:01:24Z"
    - latency: 1.185594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:00:24Z"
    - latency: 1.110875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T12:59:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T12:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.ec2.internal
      uid: 3693b7eb-b829-4a90-be42-bf466d015ebf
    resourceVersion: "26224"
    uid: 58acc0ea-e998-409f-99c9-d4e3f21d2d32
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6p7pz
    targetEndpoint: ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T12:39:24Z"
      message: 'load-balancer-api-external: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.167603ms
      message: 'load-balancer-api-external: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:09:24Z"
    - latency: 14.809261ms
      message: 'load-balancer-api-external: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:09:24Z"
    - latency: 4.861046ms
      message: 'load-balancer-api-external: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 7.08854ms
      message: 'load-balancer-api-external: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 4.732251ms
      message: 'load-balancer-api-external: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 6.733453ms
      message: 'load-balancer-api-external: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 5.706515ms
      message: 'load-balancer-api-external: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 6.701335ms
      message: 'load-balancer-api-external: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 6.623688ms
      message: 'load-balancer-api-external: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:05:24Z"
    - latency: 11.584639ms
      message: 'load-balancer-api-external: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:05:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T12:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.ec2.internal
      uid: 3693b7eb-b829-4a90-be42-bf466d015ebf
    resourceVersion: "26225"
    uid: 7879a13c-a98d-4d26-9a8d-06a58af1508d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6p7pz
    targetEndpoint: ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T12:39:24Z"
      message: 'load-balancer-api-internal: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.797739ms
      message: 'load-balancer-api-internal: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:09:24Z"
    - latency: 14.785834ms
      message: 'load-balancer-api-internal: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:09:24Z"
    - latency: 4.686618ms
      message: 'load-balancer-api-internal: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 7.054144ms
      message: 'load-balancer-api-internal: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 6.695626ms
      message: 'load-balancer-api-internal: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 6.709527ms
      message: 'load-balancer-api-internal: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 5.695176ms
      message: 'load-balancer-api-internal: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 6.683298ms
      message: 'load-balancer-api-internal: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 6.641693ms
      message: 'load-balancer-api-internal: tcp connection to ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:05:24Z"
    - latency: 11.5937ms
      message: 'load-balancer-api-internal: resolved host name ae524c6511f6a45fc8c8cc09065b71ad-7b7d250d70a5cfaf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:05:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T12:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-ip-10-0-130-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.ec2.internal
      uid: 3693b7eb-b829-4a90-be42-bf466d015ebf
    resourceVersion: "25731"
    uid: b84c4da0-a6fb-4e72-b2b5-95cf5d7a4d2b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6p7pz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T12:40:24Z"
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.146696ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 2.635758ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 2.05084ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 2.118655ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:05:24Z"
    - latency: 2.219405ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:04:24Z"
    - latency: 1.975854ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:03:24Z"
    - latency: 1.965171ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:02:24Z"
    - latency: 2.174429ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:01:24Z"
    - latency: 2.003409ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:00:24Z"
    - latency: 2.119033ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T12:59:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T12:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-ip-10-0-137-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.ec2.internal
      uid: 3693b7eb-b829-4a90-be42-bf466d015ebf
    resourceVersion: "25730"
    uid: 59563f15-7ce2-4ddf-bf2a-102d6160c92e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6p7pz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T12:40:24Z"
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.161117ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 2.207098ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 2.073949ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 2.264486ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:05:24Z"
    - latency: 2.498501ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:04:24Z"
    - latency: 2.157652ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:03:24Z"
    - latency: 2.364907ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:02:24Z"
    - latency: 2.502555ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:01:24Z"
    - latency: 2.125105ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:00:24Z"
    - latency: 2.367975ms
      message: 'network-check-target-ip-10-0-137-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T12:59:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T12:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-ip-10-0-139-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.ec2.internal
      uid: 3693b7eb-b829-4a90-be42-bf466d015ebf
    resourceVersion: "25729"
    uid: b35411a3-c99d-49ec-9300-7cd154aa3c05
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6p7pz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T12:40:24Z"
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050235ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 1.252076ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 917.344µs
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 876.436µs
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:05:24Z"
    - latency: 1.807412ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:04:24Z"
    - latency: 893.47µs
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:03:24Z"
    - latency: 996.915µs
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:02:24Z"
    - latency: 1.104558ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:01:24Z"
    - latency: 922.768µs
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:00:24Z"
    - latency: 951.11µs
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T12:59:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T12:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.ec2.internal
      uid: 3693b7eb-b829-4a90-be42-bf466d015ebf
    resourceVersion: "26223"
    uid: 7faa48c0-d894-47e3-a265-e848772e5e5a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6p7pz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T12:39:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049909ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:09:24Z"
    - latency: 1.982252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:09:24Z"
    - latency: 799.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 2.018268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:08:24Z"
    - latency: 1.439806ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 1.875895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:07:24Z"
    - latency: 954.226µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 1.902073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:06:24Z"
    - latency: 963.294µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:05:24Z"
    - latency: 1.90472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:05:24Z"
kind: List
metadata:
  resourceVersion: ""