apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:55:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: ccc9a72b-22da-4253-8680-848be47a88c2
    resourceVersion: "27843"
    uid: d85e8a7a-0a94-4d4d-b35b-11b2153b8ebd
  spec:
    sourcePod: network-check-source-56499946bc-5xfsb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:02:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.384709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:09:12Z"
    - latency: 996.097µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:08:12Z"
    - latency: 1.32143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 1.057052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 810.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 913.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 1.324414ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:12Z"
    - latency: 1.084555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:12Z"
    - latency: 882.93µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:12Z"
    - latency: 949.76µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:55:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: ccc9a72b-22da-4253-8680-848be47a88c2
    resourceVersion: "26636"
    uid: a5ff6fe4-75b9-46cb-94bc-68b46427ac26
  spec:
    sourcePod: network-check-source-56499946bc-5xfsb
    targetEndpoint: a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:01:12Z"
      message: 'load-balancer-api-external: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.683169ms
      message: 'load-balancer-api-external: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 8.084145ms
      message: 'load-balancer-api-external: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 5.039029ms
      message: 'load-balancer-api-external: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 8.246351ms
      message: 'load-balancer-api-external: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 5.994029ms
      message: 'load-balancer-api-external: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 8.744342ms
      message: 'load-balancer-api-external: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 5.139112ms
      message: 'load-balancer-api-external: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 8.009981ms
      message: 'load-balancer-api-external: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 5.542181ms
      message: 'load-balancer-api-external: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:12Z"
    - latency: 8.577572ms
      message: 'load-balancer-api-external: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:03:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:55:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: ccc9a72b-22da-4253-8680-848be47a88c2
    resourceVersion: "26637"
    uid: 869bdcf2-986e-4d1d-8594-2a74fe9eb329
  spec:
    sourcePod: network-check-source-56499946bc-5xfsb
    targetEndpoint: a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:01:12Z"
      message: 'load-balancer-api-internal: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.635298ms
      message: 'load-balancer-api-internal: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 8.010804ms
      message: 'load-balancer-api-internal: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 5.081301ms
      message: 'load-balancer-api-internal: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 8.174551ms
      message: 'load-balancer-api-internal: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 6.139761ms
      message: 'load-balancer-api-internal: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 8.770229ms
      message: 'load-balancer-api-internal: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 6.213768ms
      message: 'load-balancer-api-internal: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 7.960197ms
      message: 'load-balancer-api-internal: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 5.341099ms
      message: 'load-balancer-api-internal: tcp connection to a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:12Z"
    - latency: 8.488459ms
      message: 'load-balancer-api-internal: resolved host name a935d680075ac4827932b0bbefa4c5f3-de401ce1c3a8d24d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:03:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:55:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-ip-10-0-135-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: ccc9a72b-22da-4253-8680-848be47a88c2
    resourceVersion: "27840"
    uid: 72e404c8-2980-4918-abfe-87dd392d762b
  spec:
    sourcePod: network-check-source-56499946bc-5xfsb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:02:12Z"
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.966µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:09:12Z"
    - latency: 872.802µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:08:12Z"
    - latency: 1.082213ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 760.916µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 1.303093ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 730.999µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 776.711µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:12Z"
    - latency: 943.574µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:12Z"
    - latency: 885.833µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:12Z"
    - latency: 1.559912ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-ip-10-0-136-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: ccc9a72b-22da-4253-8680-848be47a88c2
    resourceVersion: "27841"
    uid: 76d67a41-b19d-4216-b88e-c0c23d2a2f52
  spec:
    sourcePod: network-check-source-56499946bc-5xfsb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:02:12Z"
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.183496ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:09:12Z"
    - latency: 1.809009ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:08:12Z"
    - latency: 2.209089ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 1.909867ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 2.022711ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 2.415849ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 2.311343ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:12Z"
    - latency: 2.062096ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:12Z"
    - latency: 2.219927ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:12Z"
    - latency: 2.293114ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:55:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-ip-10-0-141-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: ccc9a72b-22da-4253-8680-848be47a88c2
    resourceVersion: "27842"
    uid: 070da7ba-a322-46b7-b49d-a03e327b1d89
  spec:
    sourcePod: network-check-source-56499946bc-5xfsb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:02:12Z"
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.216844ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:09:12Z"
    - latency: 1.96942ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:08:12Z"
    - latency: 2.012363ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 2.159384ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 2.151147ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 2.419504ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 2.350068ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:12Z"
    - latency: 2.068937ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:12Z"
    - latency: 2.063279ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:12Z"
    - latency: 2.444364ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:55:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: ccc9a72b-22da-4253-8680-848be47a88c2
    resourceVersion: "26635"
    uid: 1d76630d-3a51-4ea8-a7cb-4c138a73b8a9
  spec:
    sourcePod: network-check-source-56499946bc-5xfsb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:01:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.077µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 1.770755ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:07:12Z"
    - latency: 881.055µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 1.841983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:06:12Z"
    - latency: 995.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 2.099741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:05:12Z"
    - latency: 1.32618ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 1.70576ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:04:12Z"
    - latency: 1.100605ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:12Z"
    - latency: 1.692911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:03:12Z"
kind: List
metadata:
  resourceVersion: ""