apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T15:17:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-254.ec2.internal
      uid: 4b5ace6f-79cd-45e6-ada1-d455b51b7a62
    resourceVersion: "43946"
    uid: de4c8bc6-d3bb-4f03-b5e7-8370c86716d9
  spec:
    sourcePod: network-check-source-7b678d77c7-vr69z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:24:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.636µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 857.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 986.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:43:52Z"
    - latency: 1.110248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:42:52Z"
    - latency: 1.762949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:41:52Z"
    - latency: 844.646µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:40:52Z"
    - latency: 1.157959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:39:52Z"
    - latency: 883.082µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:38:52Z"
    - latency: 741.042µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:37:52Z"
    - latency: 908.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:36:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T15:17:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-254.ec2.internal
      uid: 4b5ace6f-79cd-45e6-ada1-d455b51b7a62
    resourceVersion: "46041"
    uid: 2796e75e-1a7f-49e2-8081-c5ffd62cf00e
  spec:
    sourcePod: network-check-source-7b678d77c7-vr69z
    targetEndpoint: a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:23:52Z"
      message: 'load-balancer-api-external: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.476697ms
      message: 'load-balancer-api-external: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:47:52Z"
    - latency: 6.621015ms
      message: 'load-balancer-api-external: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:47:52Z"
    - latency: 4.786606ms
      message: 'load-balancer-api-external: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:46:52Z"
    - latency: 5.916241ms
      message: 'load-balancer-api-external: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:46:52Z"
    - latency: 4.412152ms
      message: 'load-balancer-api-external: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 6.662687ms
      message: 'load-balancer-api-external: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 4.734786ms
      message: 'load-balancer-api-external: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 8.807482ms
      message: 'load-balancer-api-external: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 3.613351ms
      message: 'load-balancer-api-external: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:43:52Z"
    - latency: 7.135309ms
      message: 'load-balancer-api-external: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:43:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T15:17:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-254.ec2.internal
      uid: 4b5ace6f-79cd-45e6-ada1-d455b51b7a62
    resourceVersion: "46042"
    uid: 8be0278e-67c6-4dab-81a8-a32631684fb9
  spec:
    sourcePod: network-check-source-7b678d77c7-vr69z
    targetEndpoint: a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:23:52Z"
      message: 'load-balancer-api-internal: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.423278ms
      message: 'load-balancer-api-internal: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:47:52Z"
    - latency: 6.694166ms
      message: 'load-balancer-api-internal: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:47:52Z"
    - latency: 4.817645ms
      message: 'load-balancer-api-internal: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:46:52Z"
    - latency: 5.867271ms
      message: 'load-balancer-api-internal: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:46:52Z"
    - latency: 3.136283ms
      message: 'load-balancer-api-internal: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 6.704227ms
      message: 'load-balancer-api-internal: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 5.148359ms
      message: 'load-balancer-api-internal: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 8.85313ms
      message: 'load-balancer-api-internal: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 4.01054ms
      message: 'load-balancer-api-internal: tcp connection to a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:43:52Z"
    - latency: 7.06298ms
      message: 'load-balancer-api-internal: resolved host name a86352aa4e13340bc8c1273c25b893dd-7b2089feff735772.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:43:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T15:17:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-254-to-network-check-target-ip-10-0-129-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-254.ec2.internal
      uid: 4b5ace6f-79cd-45e6-ada1-d455b51b7a62
    resourceVersion: "43943"
    uid: 6d578c88-fc98-44f4-8f39-3c5061f6c8f4
  spec:
    sourcePod: network-check-source-7b678d77c7-vr69z
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:24:52Z"
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.391µs
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 1.219327ms
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 1.787808ms
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:43:52Z"
    - latency: 899.683µs
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:42:52Z"
    - latency: 1.019919ms
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:41:52Z"
    - latency: 833.689µs
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:40:52Z"
    - latency: 828.456µs
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:39:52Z"
    - latency: 968.894µs
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:38:52Z"
    - latency: 748.586µs
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:37:52Z"
    - latency: 1.017791ms
      message: 'network-check-target-ip-10-0-129-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:36:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T15:17:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-254-to-network-check-target-ip-10-0-135-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-254.ec2.internal
      uid: 4b5ace6f-79cd-45e6-ada1-d455b51b7a62
    resourceVersion: "43945"
    uid: 5478f2a2-d7ac-43f6-bd5a-1a0f625d7f60
  spec:
    sourcePod: network-check-source-7b678d77c7-vr69z
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:24:52Z"
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.251154ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 2.052729ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 2.094446ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:43:52Z"
    - latency: 2.18948ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:42:52Z"
    - latency: 2.282938ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:41:52Z"
    - latency: 2.205954ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:40:52Z"
    - latency: 2.380758ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:39:52Z"
    - latency: 2.137412ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:38:52Z"
    - latency: 2.163624ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:37:52Z"
    - latency: 2.612401ms
      message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:36:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T15:17:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-254-to-network-check-target-ip-10-0-136-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-254.ec2.internal
      uid: 4b5ace6f-79cd-45e6-ada1-d455b51b7a62
    resourceVersion: "43944"
    uid: 66a107fb-7cd7-418c-b76b-0ce9b4445018
  spec:
    sourcePod: network-check-source-7b678d77c7-vr69z
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:24:52Z"
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.31623ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 2.315139ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 2.425102ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:43:52Z"
    - latency: 2.320158ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:42:52Z"
    - latency: 2.854736ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:41:52Z"
    - latency: 2.305091ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:40:52Z"
    - latency: 2.330186ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:39:52Z"
    - latency: 2.362894ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:38:52Z"
    - latency: 2.244863ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:37:52Z"
    - latency: 2.230019ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:36:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T15:17:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-254.ec2.internal
      uid: 4b5ace6f-79cd-45e6-ada1-d455b51b7a62
    resourceVersion: "46040"
    uid: c08e7ddc-16c7-4f37-84d5-5b166203ac18
  spec:
    sourcePod: network-check-source-7b678d77c7-vr69z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:23:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.456µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:47:52Z"
    - latency: 1.903295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:47:52Z"
    - latency: 809.758µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:46:52Z"
    - latency: 1.621852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:46:52Z"
    - latency: 905.108µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 1.82824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:45:52Z"
    - latency: 1.232757ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 1.689905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:44:52Z"
    - latency: 932.954µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:43:52Z"
    - latency: 1.653554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:43:52Z"
kind: List
metadata:
  resourceVersion: ""