apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:30:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 8f3a99d2-ba8a-408c-8331-8341732c5643
    resourceVersion: "68351"
    uid: eea9ce41-44b2-4235-9481-fbf8bd6f2f3b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7l2l4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:37:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.381091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:33Z"
    - latency: 936.114µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 1.356894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 1.167822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 1.409047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 1.605501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:33Z"
    - latency: 1.265075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:33Z"
    - latency: 1.499331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:12:33Z"
    - latency: 1.026744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:11:33Z"
    - latency: 1.231269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:30:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 8f3a99d2-ba8a-408c-8331-8341732c5643
    resourceVersion: "67317"
    uid: bc56ffd4-1e4c-41b3-ac93-2c6766ab12f4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7l2l4
    targetEndpoint: a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:36:33Z"
      message: 'load-balancer-api-external: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.053038ms
      message: 'load-balancer-api-external: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 9.539296ms
      message: 'load-balancer-api-external: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 4.496291ms
      message: 'load-balancer-api-external: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 6.580186ms
      message: 'load-balancer-api-external: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 6.127381ms
      message: 'load-balancer-api-external: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 7.435697ms
      message: 'load-balancer-api-external: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 5.719332ms
      message: 'load-balancer-api-external: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 7.33916ms
      message: 'load-balancer-api-external: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 5.155523ms
      message: 'load-balancer-api-external: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:33Z"
    - latency: 6.345417ms
      message: 'load-balancer-api-external: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:14:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:30:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 8f3a99d2-ba8a-408c-8331-8341732c5643
    resourceVersion: "67318"
    uid: e8195d04-d999-4a81-8123-06b84fc6a579
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7l2l4
    targetEndpoint: a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:36:33Z"
      message: 'load-balancer-api-internal: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.077854ms
      message: 'load-balancer-api-internal: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 9.595111ms
      message: 'load-balancer-api-internal: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 3.727137ms
      message: 'load-balancer-api-internal: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 6.527257ms
      message: 'load-balancer-api-internal: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 6.196737ms
      message: 'load-balancer-api-internal: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 7.317614ms
      message: 'load-balancer-api-internal: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 5.710692ms
      message: 'load-balancer-api-internal: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 7.256967ms
      message: 'load-balancer-api-internal: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 5.156015ms
      message: 'load-balancer-api-internal: tcp connection to a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:33Z"
    - latency: 6.410308ms
      message: 'load-balancer-api-internal: resolved host name a3bccbe94d59a46bda5e13fc8da00b55-9af25ed474316475.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:14:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:30:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-ip-10-0-130-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 8f3a99d2-ba8a-408c-8331-8341732c5643
    resourceVersion: "68350"
    uid: 6219aa6e-ee81-4fa3-9a6b-478722c48606
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7l2l4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:37:33Z"
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.861133ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:33Z"
    - latency: 2.394629ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 2.635604ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 2.161217ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 2.451548ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 2.361922ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:33Z"
    - latency: 2.560148ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:33Z"
    - latency: 2.707269ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:12:33Z"
    - latency: 2.309641ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:11:33Z"
    - latency: 2.508876ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:30:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-ip-10-0-139-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 8f3a99d2-ba8a-408c-8331-8341732c5643
    resourceVersion: "68348"
    uid: 171cea42-0c9e-48d7-9fef-ecbadae1e56e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7l2l4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:37:33Z"
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127961ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:33Z"
    - latency: 1.014578ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 1.053133ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 954.832µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 1.014583ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 969.595µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:33Z"
    - latency: 920.827µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:33Z"
    - latency: 917.727µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:12:33Z"
    - latency: 1.011108ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:11:33Z"
    - latency: 815.067µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:30:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-ip-10-0-139-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 8f3a99d2-ba8a-408c-8331-8341732c5643
    resourceVersion: "68349"
    uid: 7b8980a7-b7d6-4018-9987-fbee59ace0bb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7l2l4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:37:33Z"
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.262887ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:33Z"
    - latency: 2.335055ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 2.39298ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 2.196281ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 2.1871ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 2.244079ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:33Z"
    - latency: 2.40856ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:33Z"
    - latency: 2.257774ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:12:33Z"
    - latency: 2.0908ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:11:33Z"
    - latency: 2.051531ms
      message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:30:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 8f3a99d2-ba8a-408c-8331-8341732c5643
    resourceVersion: "67316"
    uid: f764cd78-f6ab-4ac2-9282-2ba5cbd474b7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7l2l4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:36:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 961.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 2.232741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:18:33Z"
    - latency: 961.694µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 1.785956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:17:33Z"
    - latency: 1.077231ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 2.079119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:16:33Z"
    - latency: 1.041529ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 2.116992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:15:33Z"
    - latency: 1.114855ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:33Z"
    - latency: 1.890164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:14:33Z"
kind: List
metadata:
  resourceVersion: ""