apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:09:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-124-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-124.ec2.internal
      uid: bb2719ff-a932-4c08-8bed-82eea3a96cc6
    resourceVersion: "67889"
    uid: 9cfdb9a7-c4f1-4f89-bdbb-63e8aa2131f5
  spec:
    sourcePod: network-check-source-6f8b768455-46z86
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:16:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.238292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 1.327366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 1.227774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 1.110817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:56Z"
    - latency: 2.007018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:40:56Z"
    - latency: 998.873µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:56Z"
    - latency: 1.476193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:56Z"
    - latency: 2.212669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:56Z"
    - latency: 1.055895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:56Z"
    - latency: 1.448251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:09:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-124-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-124.ec2.internal
      uid: bb2719ff-a932-4c08-8bed-82eea3a96cc6
    resourceVersion: "68866"
    uid: d6b571eb-e3f6-47a1-a9b0-30f2182fdc88
  spec:
    sourcePod: network-check-source-6f8b768455-46z86
    targetEndpoint: afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:15:56Z"
      message: 'load-balancer-api-external: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.189172ms
      message: 'load-balancer-api-external: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:45:56Z"
    - latency: 7.51856ms
      message: 'load-balancer-api-external: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:45:56Z"
    - latency: 5.696793ms
      message: 'load-balancer-api-external: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 6.989197ms
      message: 'load-balancer-api-external: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 5.44122ms
      message: 'load-balancer-api-external: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 5.663995ms
      message: 'load-balancer-api-external: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 4.456002ms
      message: 'load-balancer-api-external: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 8.082356ms
      message: 'load-balancer-api-external: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 5.273175ms
      message: 'load-balancer-api-external: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:56Z"
    - latency: 6.638538ms
      message: 'load-balancer-api-external: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:41:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:09:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-124-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-124.ec2.internal
      uid: bb2719ff-a932-4c08-8bed-82eea3a96cc6
    resourceVersion: "68865"
    uid: 6cac8684-1b66-4249-9525-669bdab3a626
  spec:
    sourcePod: network-check-source-6f8b768455-46z86
    targetEndpoint: afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:15:56Z"
      message: 'load-balancer-api-internal: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.078765ms
      message: 'load-balancer-api-internal: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:45:56Z"
    - latency: 7.617258ms
      message: 'load-balancer-api-internal: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:45:56Z"
    - latency: 5.226132ms
      message: 'load-balancer-api-internal: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 6.905252ms
      message: 'load-balancer-api-internal: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 5.437286ms
      message: 'load-balancer-api-internal: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 5.757766ms
      message: 'load-balancer-api-internal: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 4.50481ms
      message: 'load-balancer-api-internal: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 7.898197ms
      message: 'load-balancer-api-internal: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 5.247703ms
      message: 'load-balancer-api-internal: tcp connection to afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:56Z"
    - latency: 6.618621ms
      message: 'load-balancer-api-internal: resolved host name afc67b04920454e0e9ce5956e83f8373-a614ccce49fab074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:41:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:09:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-124-to-network-check-target-ip-10-0-134-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-124.ec2.internal
      uid: bb2719ff-a932-4c08-8bed-82eea3a96cc6
    resourceVersion: "67888"
    uid: f7b30295-cafe-4c13-a0d2-74a1bfb87fb9
  spec:
    sourcePod: network-check-source-6f8b768455-46z86
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:16:56Z"
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.924542ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 1.966216ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 1.928018ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 1.813177ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:56Z"
    - latency: 1.773388ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:40:56Z"
    - latency: 2.094393ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:56Z"
    - latency: 2.143948ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:56Z"
    - latency: 2.173099ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:56Z"
    - latency: 2.07642ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:56Z"
    - latency: 2.043477ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:09:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-124-to-network-check-target-ip-10-0-140-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-124.ec2.internal
      uid: bb2719ff-a932-4c08-8bed-82eea3a96cc6
    resourceVersion: "67886"
    uid: ac341ee8-c4cd-443e-9499-b4b58612d6b5
  spec:
    sourcePod: network-check-source-6f8b768455-46z86
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:16:56Z"
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.99µs
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 1.042827ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 1.111523ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 1.051519ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:56Z"
    - latency: 982.557µs
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:40:56Z"
    - latency: 1.242068ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:56Z"
    - latency: 1.159206ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:56Z"
    - latency: 1.159495ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:56Z"
    - latency: 1.19812ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:56Z"
    - latency: 1.448068ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:09:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-124-to-network-check-target-ip-10-0-141-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-124.ec2.internal
      uid: bb2719ff-a932-4c08-8bed-82eea3a96cc6
    resourceVersion: "67887"
    uid: dcedbef2-a742-4cbb-98f2-596ac8e75680
  spec:
    sourcePod: network-check-source-6f8b768455-46z86
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:16:56Z"
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.300462ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 2.21493ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 2.030365ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 2.427884ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:56Z"
    - latency: 2.199848ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:40:56Z"
    - latency: 2.744812ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:56Z"
    - latency: 2.584352ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:56Z"
    - latency: 2.094302ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:56Z"
    - latency: 2.42444ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:56Z"
    - latency: 2.642497ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:09:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-124-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-124.ec2.internal
      uid: bb2719ff-a932-4c08-8bed-82eea3a96cc6
    resourceVersion: "68864"
    uid: 36a09e3d-d8bd-4cbf-8c98-ff056607d963
  spec:
    sourcePod: network-check-source-6f8b768455-46z86
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:15:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.57µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:45:56Z"
    - latency: 1.890811ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:45:56Z"
    - latency: 1.220091ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 1.992511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:44:56Z"
    - latency: 1.202891ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 1.711001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:43:56Z"
    - latency: 937.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 1.924132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:42:56Z"
    - latency: 1.043924ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:56Z"
    - latency: 1.689403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:41:56Z"
kind: List
metadata:
  resourceVersion: ""