apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T09:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-81-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-81.ec2.internal
      uid: 88a17dfb-72bc-4191-ad44-723cd7d87b17
    resourceVersion: "54878"
    uid: d4a18bf6-4a12-4c77-b7ed-622f9be65780
  spec:
    sourcePod: network-check-source-685456655f-6ds2f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T09:10:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 979.271µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 1.265769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:29:01Z"
    - latency: 1.11935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:28:01Z"
    - latency: 1.148197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:27:01Z"
    - latency: 816.018µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:26:01Z"
    - latency: 807.722µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:25:01Z"
    - latency: 833.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:24:01Z"
    - latency: 1.272227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:23:01Z"
    - latency: 899.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:22:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T09:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-81-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-81.ec2.internal
      uid: 88a17dfb-72bc-4191-ad44-723cd7d87b17
    resourceVersion: "56417"
    uid: fa191529-d02d-4b9c-9ceb-2abc38869931
  spec:
    sourcePod: network-check-source-685456655f-6ds2f
    targetEndpoint: ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T09:09:01Z"
      message: 'load-balancer-api-external: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.44509ms
      message: 'load-balancer-api-external: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:33:01Z"
    - latency: 8.064812ms
      message: 'load-balancer-api-external: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:33:01Z"
    - latency: 4.332053ms
      message: 'load-balancer-api-external: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:32:01Z"
    - latency: 9.437291ms
      message: 'load-balancer-api-external: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:32:01Z"
    - latency: 4.059051ms
      message: 'load-balancer-api-external: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 8.125553ms
      message: 'load-balancer-api-external: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 3.974038ms
      message: 'load-balancer-api-external: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 7.735913ms
      message: 'load-balancer-api-external: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 3.944223ms
      message: 'load-balancer-api-external: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:29:01Z"
    - latency: 8.309742ms
      message: 'load-balancer-api-external: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:29:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T09:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-81-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-81.ec2.internal
      uid: 88a17dfb-72bc-4191-ad44-723cd7d87b17
    resourceVersion: "56418"
    uid: 28cc30b3-eab9-4cfd-8b95-2b3d568a2624
  spec:
    sourcePod: network-check-source-685456655f-6ds2f
    targetEndpoint: ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T09:09:01Z"
      message: 'load-balancer-api-internal: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.39388ms
      message: 'load-balancer-api-internal: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:33:01Z"
    - latency: 8.092415ms
      message: 'load-balancer-api-internal: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:33:01Z"
    - latency: 4.49974ms
      message: 'load-balancer-api-internal: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:32:01Z"
    - latency: 9.535016ms
      message: 'load-balancer-api-internal: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:32:01Z"
    - latency: 3.542193ms
      message: 'load-balancer-api-internal: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 8.034599ms
      message: 'load-balancer-api-internal: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 3.240407ms
      message: 'load-balancer-api-internal: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 7.678879ms
      message: 'load-balancer-api-internal: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 3.896221ms
      message: 'load-balancer-api-internal: tcp connection to ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:29:01Z"
    - latency: 8.348219ms
      message: 'load-balancer-api-internal: resolved host name ab77b5db5920c49299b333956790f3eb-6d8126a272c2f933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:29:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T09:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-81-to-network-check-target-ip-10-0-131-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-81.ec2.internal
      uid: 88a17dfb-72bc-4191-ad44-723cd7d87b17
    resourceVersion: "54875"
    uid: 29a2c7db-94b9-4b96-8e8f-a07356f78f69
  spec:
    sourcePod: network-check-source-685456655f-6ds2f
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T09:10:01Z"
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.028654ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 2.227365ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 2.523127ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:29:01Z"
    - latency: 2.441449ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:28:01Z"
    - latency: 2.231654ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:27:01Z"
    - latency: 2.057769ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:26:01Z"
    - latency: 1.742279ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:25:01Z"
    - latency: 2.304366ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:24:01Z"
    - latency: 2.248979ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:23:01Z"
    - latency: 2.163386ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:22:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T09:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-81-to-network-check-target-ip-10-0-138-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-81.ec2.internal
      uid: 88a17dfb-72bc-4191-ad44-723cd7d87b17
    resourceVersion: "54877"
    uid: 8847f482-b698-4a57-80f6-29950dc05493
  spec:
    sourcePod: network-check-source-685456655f-6ds2f
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T09:10:01Z"
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.383504ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 2.808882ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 2.439451ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:29:01Z"
    - latency: 2.276291ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:28:01Z"
    - latency: 2.183389ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:27:01Z"
    - latency: 2.268415ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:26:01Z"
    - latency: 2.026211ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:25:01Z"
    - latency: 3.403542ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:24:01Z"
    - latency: 2.31051ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:23:01Z"
    - latency: 2.118445ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:22:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T09:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-81-to-network-check-target-ip-10-0-141-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-81.ec2.internal
      uid: 88a17dfb-72bc-4191-ad44-723cd7d87b17
    resourceVersion: "54876"
    uid: bc577237-d285-4072-8fc2-0e5a37dbff6a
  spec:
    sourcePod: network-check-source-685456655f-6ds2f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T09:10:01Z"
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.844µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 1.197924ms
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 948.896µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:29:01Z"
    - latency: 810.774µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:28:01Z"
    - latency: 846.352µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:27:01Z"
    - latency: 885.509µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:26:01Z"
    - latency: 941.846µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:25:01Z"
    - latency: 1.478968ms
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:24:01Z"
    - latency: 988.175µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:23:01Z"
    - latency: 993.698µs
      message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:22:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T09:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-81-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-81.ec2.internal
      uid: 88a17dfb-72bc-4191-ad44-723cd7d87b17
    resourceVersion: "56416"
    uid: a15568b0-1732-459d-af8a-1621c8ee71b8
  spec:
    sourcePod: network-check-source-685456655f-6ds2f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T09:09:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.317213ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:33:01Z"
    - latency: 1.753091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:33:01Z"
    - latency: 742.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:32:01Z"
    - latency: 1.646025ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:32:01Z"
    - latency: 1.121997ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 1.739152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:31:01Z"
    - latency: 733.121µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 1.568063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:30:01Z"
    - latency: 888.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T09:29:01Z"
    - latency: 1.724857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T09:29:01Z"
kind: List
metadata:
  resourceVersion: ""