apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:57:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 712990ab-39be-4270-a658-075725775ba8
    resourceVersion: "61153"
    uid: d6e8f157-c4a8-4876-a8e2-0090ba8420c0
  spec:
    sourcePod: network-check-source-869dcfcdcd-qgx9n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:04:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.220954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 896.276µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 1.162827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 1.218978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 1.417281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:35:26Z"
    - latency: 1.332234ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:34:26Z"
    - latency: 844.88µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:33:26Z"
    - latency: 1.109692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:32:26Z"
    - latency: 1.01885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:31:26Z"
    - latency: 1.098531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:57:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 712990ab-39be-4270-a658-075725775ba8
    resourceVersion: "61155"
    uid: b84cc96f-66d9-4cb1-b950-41b3bd426196
  spec:
    sourcePod: network-check-source-869dcfcdcd-qgx9n
    targetEndpoint: a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:03:26Z"
      message: 'load-balancer-api-external: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.007404ms
      message: 'load-balancer-api-external: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 7.343789ms
      message: 'load-balancer-api-external: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 4.215695ms
      message: 'load-balancer-api-external: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 7.945379ms
      message: 'load-balancer-api-external: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 3.401757ms
      message: 'load-balancer-api-external: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 9.263601ms
      message: 'load-balancer-api-external: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 3.840872ms
      message: 'load-balancer-api-external: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 7.627959ms
      message: 'load-balancer-api-external: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 4.047796ms
      message: 'load-balancer-api-external: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:35:26Z"
    - latency: 7.80954ms
      message: 'load-balancer-api-external: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:35:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:57:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 712990ab-39be-4270-a658-075725775ba8
    resourceVersion: "61154"
    uid: c95c3b81-e65a-4994-a764-ab4da8f7b395
  spec:
    sourcePod: network-check-source-869dcfcdcd-qgx9n
    targetEndpoint: a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:03:26Z"
      message: 'load-balancer-api-internal: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.764327ms
      message: 'load-balancer-api-internal: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 7.388051ms
      message: 'load-balancer-api-internal: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 3.88962ms
      message: 'load-balancer-api-internal: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 7.914798ms
      message: 'load-balancer-api-internal: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 3.809543ms
      message: 'load-balancer-api-internal: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 9.236248ms
      message: 'load-balancer-api-internal: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 3.725199ms
      message: 'load-balancer-api-internal: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 7.716102ms
      message: 'load-balancer-api-internal: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 4.32848ms
      message: 'load-balancer-api-internal: tcp connection to a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:35:26Z"
    - latency: 7.766144ms
      message: 'load-balancer-api-internal: resolved host name a7045152d19c040bba238bd65d9aca5b-b84b9950b1723fbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:35:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:57:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-128-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 712990ab-39be-4270-a658-075725775ba8
    resourceVersion: "61152"
    uid: d440cd88-38b8-43dd-a067-3d0898d546e6
  spec:
    sourcePod: network-check-source-869dcfcdcd-qgx9n
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:04:26Z"
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.400976ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 2.406311ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 2.373149ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 2.29609ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 2.283859ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:35:26Z"
    - latency: 2.259091ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:34:26Z"
    - latency: 2.542977ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:33:26Z"
    - latency: 2.557919ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:32:26Z"
    - latency: 3.091083ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:31:26Z"
    - latency: 2.344721ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:57:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-128-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 712990ab-39be-4270-a658-075725775ba8
    resourceVersion: "61149"
    uid: 27a847dc-afbb-4ac8-91f5-cbe19c0eb48e
  spec:
    sourcePod: network-check-source-869dcfcdcd-qgx9n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:04:26Z"
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.157µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 900.563µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 1.33961ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 935.497µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 921.202µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:35:26Z"
    - latency: 1.317138ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:34:26Z"
    - latency: 1.051393ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:33:26Z"
    - latency: 839.279µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:32:26Z"
    - latency: 821.375µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:31:26Z"
    - latency: 836.661µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:57:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-142-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 712990ab-39be-4270-a658-075725775ba8
    resourceVersion: "61150"
    uid: 7dee4544-17eb-4b08-b112-ce5148615247
  spec:
    sourcePod: network-check-source-869dcfcdcd-qgx9n
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:04:26Z"
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.406807ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 2.446345ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 2.610808ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 2.365632ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 2.22126ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:35:26Z"
    - latency: 2.372761ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:34:26Z"
    - latency: 2.575946ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:33:26Z"
    - latency: 2.251921ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:32:26Z"
    - latency: 2.404799ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:31:26Z"
    - latency: 2.59281ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:57:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 712990ab-39be-4270-a658-075725775ba8
    resourceVersion: "61151"
    uid: 1445ae5d-ff70-4703-bee4-1fff8216c348
  spec:
    sourcePod: network-check-source-869dcfcdcd-qgx9n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:03:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 2.04683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:39:26Z"
    - latency: 1.061735ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 2.21046ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:38:26Z"
    - latency: 871.505µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 1.629819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:37:26Z"
    - latency: 813.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 1.942158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:36:26Z"
    - latency: 1.245824ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:35:26Z"
    - latency: 1.747803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:35:26Z"
kind: List
metadata:
  resourceVersion: ""