apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:28:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: ca60dfad-4875-43e1-8219-c48333981be4
    resourceVersion: "22764"
    uid: 1e4ffe63-74ec-4f57-8ca9-c94527b52d56
  spec:
    sourcePod: network-check-source-56499946bc-2d6jr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:35: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.167368ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:49:26Z"
    - latency: 1.252395ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:26Z"
    - latency: 1.233034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:26Z"
    - latency: 1.109554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 1.236307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 1.161511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 1.088669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 1.678029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:26Z"
    - latency: 919.53µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:26Z"
    - latency: 1.211383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:28:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: ca60dfad-4875-43e1-8219-c48333981be4
    resourceVersion: "21351"
    uid: 3712fdd2-f559-4eb9-bd64-a00460b4dcac
  spec:
    sourcePod: network-check-source-56499946bc-2d6jr
    targetEndpoint: aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:34:26Z"
      message: 'load-balancer-api-external: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.685686ms
      message: 'load-balancer-api-external: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 8.619243ms
      message: 'load-balancer-api-external: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 4.775499ms
      message: 'load-balancer-api-external: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 8.30046ms
      message: 'load-balancer-api-external: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 5.278529ms
      message: 'load-balancer-api-external: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 9.409501ms
      message: 'load-balancer-api-external: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 5.288756ms
      message: 'load-balancer-api-external: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 7.268398ms
      message: 'load-balancer-api-external: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 4.259632ms
      message: 'load-balancer-api-external: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:26Z"
    - latency: 9.643517ms
      message: 'load-balancer-api-external: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:28:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: ca60dfad-4875-43e1-8219-c48333981be4
    resourceVersion: "21352"
    uid: d87098ba-e2e9-4612-8331-a85d4f768524
  spec:
    sourcePod: network-check-source-56499946bc-2d6jr
    targetEndpoint: aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:34:26Z"
      message: 'load-balancer-api-internal: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.579834ms
      message: 'load-balancer-api-internal: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 8.691675ms
      message: 'load-balancer-api-internal: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 4.512798ms
      message: 'load-balancer-api-internal: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 8.252103ms
      message: 'load-balancer-api-internal: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 4.747162ms
      message: 'load-balancer-api-internal: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 9.359264ms
      message: 'load-balancer-api-internal: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 5.318907ms
      message: 'load-balancer-api-internal: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 7.198535ms
      message: 'load-balancer-api-internal: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 3.70745ms
      message: 'load-balancer-api-internal: tcp connection to aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:26Z"
    - latency: 9.755818ms
      message: 'load-balancer-api-internal: resolved host name aa6cc3d5221304c4bbf2981f616ffa96-12c4865dbcced5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:28:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-ip-10-0-132-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: ca60dfad-4875-43e1-8219-c48333981be4
    resourceVersion: "22763"
    uid: 9df7985c-c0cf-45e2-bb22-277ede764665
  spec:
    sourcePod: network-check-source-56499946bc-2d6jr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:35:26Z"
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.060935ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:49:26Z"
    - latency: 1.852591ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:26Z"
    - latency: 1.897123ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:26Z"
    - latency: 1.81468ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 1.836312ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 2.002886ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 1.903426ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 2.874238ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:26Z"
    - latency: 1.814445ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:26Z"
    - latency: 1.731224ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:28:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-ip-10-0-138-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: ca60dfad-4875-43e1-8219-c48333981be4
    resourceVersion: "22761"
    uid: 7d79b68d-9819-4123-a0b8-896e44fbeefa
  spec:
    sourcePod: network-check-source-56499946bc-2d6jr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:35:26Z"
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.262µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:49:26Z"
    - latency: 882.139µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:26Z"
    - latency: 1.465899ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:26Z"
    - latency: 1.204674ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 1.639941ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 952.871µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 948.309µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 1.380871ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:26Z"
    - latency: 1.360157ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:26Z"
    - latency: 849.797µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:28:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-ip-10-0-140-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: ca60dfad-4875-43e1-8219-c48333981be4
    resourceVersion: "22762"
    uid: 94933cff-36ce-44f5-b4ee-54701cb24c63
  spec:
    sourcePod: network-check-source-56499946bc-2d6jr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:35:26Z"
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.248206ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:49:26Z"
    - latency: 2.592793ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:26Z"
    - latency: 2.24494ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:26Z"
    - latency: 2.179758ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 2.743523ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 2.312484ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 2.304749ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 3.206753ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:26Z"
    - latency: 2.344828ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:26Z"
    - latency: 2.28494ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:28:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: ca60dfad-4875-43e1-8219-c48333981be4
    resourceVersion: "21350"
    uid: a3b00532-2e4e-45f5-9169-223a9c466049
  spec:
    sourcePod: network-check-source-56499946bc-2d6jr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:34:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 764.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 1.805191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:46:26Z"
    - latency: 1.021829ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 1.731329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:26Z"
    - latency: 894.133µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 2.030555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:26Z"
    - latency: 901.193µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 1.809374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:26Z"
    - latency: 944.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:26Z"
    - latency: 3.055711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:26Z"
kind: List
metadata:
  resourceVersion: ""