apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: afd4d478-af9e-4dce-9de1-00b9fdb314b2
    resourceVersion: "22920"
    uid: 3238950c-c78e-4576-97f2-d477eafb1249
  spec:
    sourcePod: network-check-source-7cbc45fddc-km4bg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.414549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 1.05752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:23Z"
    - latency: 1.123356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:23Z"
    - latency: 902.961µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:23Z"
    - latency: 1.216569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:23Z"
    - latency: 1.269778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:23Z"
    - latency: 877.642µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:23Z"
    - latency: 1.064822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:23Z"
    - latency: 1.157127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:23Z"
    - latency: 1.834284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: afd4d478-af9e-4dce-9de1-00b9fdb314b2
    resourceVersion: "23899"
    uid: dd84aa1c-a04e-4e98-8c2a-e2afdaf74244
  spec:
    sourcePod: network-check-source-7cbc45fddc-km4bg
    targetEndpoint: a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:23Z"
      message: 'load-balancer-api-external: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.875273ms
      message: 'load-balancer-api-external: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:07:23Z"
    - latency: 7.972436ms
      message: 'load-balancer-api-external: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:07:23Z"
    - latency: 5.278924ms
      message: 'load-balancer-api-external: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:06:23Z"
    - latency: 8.938242ms
      message: 'load-balancer-api-external: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:06:23Z"
    - latency: 4.632908ms
      message: 'load-balancer-api-external: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:05:23Z"
    - latency: 9.026264ms
      message: 'load-balancer-api-external: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:05:23Z"
    - latency: 6.188637ms
      message: 'load-balancer-api-external: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 9.35857ms
      message: 'load-balancer-api-external: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 12.996602ms
      message: 'load-balancer-api-external: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:23Z"
    - latency: 8.272186ms
      message: 'load-balancer-api-external: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:03:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: afd4d478-af9e-4dce-9de1-00b9fdb314b2
    resourceVersion: "23898"
    uid: cf94d355-ed9d-4e38-8de1-5aadb09c8031
  spec:
    sourcePod: network-check-source-7cbc45fddc-km4bg
    targetEndpoint: a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:23Z"
      message: 'load-balancer-api-internal: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.957952ms
      message: 'load-balancer-api-internal: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:07:23Z"
    - latency: 7.954581ms
      message: 'load-balancer-api-internal: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:07:23Z"
    - latency: 5.483463ms
      message: 'load-balancer-api-internal: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:06:23Z"
    - latency: 8.979768ms
      message: 'load-balancer-api-internal: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:06:23Z"
    - latency: 4.621394ms
      message: 'load-balancer-api-internal: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:05:23Z"
    - latency: 9.054246ms
      message: 'load-balancer-api-internal: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:05:23Z"
    - latency: 5.65ms
      message: 'load-balancer-api-internal: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 9.464456ms
      message: 'load-balancer-api-internal: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 7.65376ms
      message: 'load-balancer-api-internal: tcp connection to a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:23Z"
    - latency: 8.327348ms
      message: 'load-balancer-api-internal: resolved host name a787ff70a1d254c20ab9cc9421dc6f21-1c4aa89569c985cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:03:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-130-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: afd4d478-af9e-4dce-9de1-00b9fdb314b2
    resourceVersion: "22917"
    uid: 0ce0accd-6fce-4a62-9cf4-4179c5f52873
  spec:
    sourcePod: network-check-source-7cbc45fddc-km4bg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:23Z"
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.37µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 982.493µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:23Z"
    - latency: 1.262335ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:23Z"
    - latency: 1.163373ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:23Z"
    - latency: 861.454µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:23Z"
    - latency: 754.663µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:23Z"
    - latency: 1.138415ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:23Z"
    - latency: 1.318078ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:23Z"
    - latency: 1.300611ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:23Z"
    - latency: 770.164µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-134-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: afd4d478-af9e-4dce-9de1-00b9fdb314b2
    resourceVersion: "22919"
    uid: b7c44f85-1168-4e6a-9220-607eb1bf4c95
  spec:
    sourcePod: network-check-source-7cbc45fddc-km4bg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:23Z"
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289214ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 2.408434ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:23Z"
    - latency: 2.147941ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:23Z"
    - latency: 2.154206ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:23Z"
    - latency: 2.320529ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:23Z"
    - latency: 2.270983ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:23Z"
    - latency: 2.020282ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:23Z"
    - latency: 2.118167ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:23Z"
    - latency: 2.030159ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:23Z"
    - latency: 1.813443ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-136-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: afd4d478-af9e-4dce-9de1-00b9fdb314b2
    resourceVersion: "22918"
    uid: fe189e93-a032-497a-91f8-185c4c4e25c4
  spec:
    sourcePod: network-check-source-7cbc45fddc-km4bg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:23Z"
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.126153ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 1.91525ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:23Z"
    - latency: 2.024266ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:23Z"
    - latency: 2.068066ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:23Z"
    - latency: 1.909894ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:23Z"
    - latency: 2.201771ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:23Z"
    - latency: 1.764203ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:23Z"
    - latency: 2.139917ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:23Z"
    - latency: 2.043343ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:23Z"
    - latency: 1.730359ms
      message: 'network-check-target-ip-10-0-136-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: afd4d478-af9e-4dce-9de1-00b9fdb314b2
    resourceVersion: "23897"
    uid: e1625c3c-df8b-4850-ab71-35820c138af1
  spec:
    sourcePod: network-check-source-7cbc45fddc-km4bg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.084µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:07:23Z"
    - latency: 1.866135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:07:23Z"
    - latency: 1.570842ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:06:23Z"
    - latency: 1.874278ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:06:23Z"
    - latency: 784.85µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:05:23Z"
    - latency: 2.793326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:05:23Z"
    - latency: 891.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 2.275058ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:04:23Z"
    - latency: 1.054147ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:23Z"
    - latency: 1.786321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:03:23Z"
kind: List
metadata:
  resourceVersion: ""