apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T21:08:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: 213d91dc-3715-4e24-9132-ee5efc2212d8
    resourceVersion: "25748"
    uid: beaa64f9-0760-4726-aa3e-8dd8ea24d2ac
  spec:
    sourcePod: network-check-source-7d88cb55d8-sbdd7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:15:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 881.623µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 1.290431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:05Z"
    - latency: 806.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:33:05Z"
    - latency: 914.53µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:32:05Z"
    - latency: 822.989µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:31:05Z"
    - latency: 1.287773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:30:05Z"
    - latency: 993.623µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:29:05Z"
    - latency: 876.372µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:28:05Z"
    - latency: 1.510314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T21:08:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: 213d91dc-3715-4e24-9132-ee5efc2212d8
    resourceVersion: "26795"
    uid: 52ae4b61-59c2-4718-8777-44144cce0817
  spec:
    sourcePod: network-check-source-7d88cb55d8-sbdd7
    targetEndpoint: aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:14:05Z"
      message: 'load-balancer-api-external: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.93185ms
      message: 'load-balancer-api-external: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:05Z"
    - latency: 11.537533ms
      message: 'load-balancer-api-external: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:38:05Z"
    - latency: 5.048813ms
      message: 'load-balancer-api-external: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:05Z"
    - latency: 12.723699ms
      message: 'load-balancer-api-external: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:37:05Z"
    - latency: 5.935912ms
      message: 'load-balancer-api-external: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 10.386459ms
      message: 'load-balancer-api-external: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 5.657607ms
      message: 'load-balancer-api-external: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 12.387435ms
      message: 'load-balancer-api-external: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 5.359634ms
      message: 'load-balancer-api-external: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:05Z"
    - latency: 10.696165ms
      message: 'load-balancer-api-external: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:34:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T21:08:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: 213d91dc-3715-4e24-9132-ee5efc2212d8
    resourceVersion: "26796"
    uid: aaba0109-2a28-434c-9e36-8bf557cd5d71
  spec:
    sourcePod: network-check-source-7d88cb55d8-sbdd7
    targetEndpoint: aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:14:05Z"
      message: 'load-balancer-api-internal: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.975566ms
      message: 'load-balancer-api-internal: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:05Z"
    - latency: 11.470508ms
      message: 'load-balancer-api-internal: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:38:05Z"
    - latency: 5.093596ms
      message: 'load-balancer-api-internal: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:05Z"
    - latency: 12.771604ms
      message: 'load-balancer-api-internal: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:37:05Z"
    - latency: 5.930439ms
      message: 'load-balancer-api-internal: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 10.353182ms
      message: 'load-balancer-api-internal: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 5.342337ms
      message: 'load-balancer-api-internal: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 12.346721ms
      message: 'load-balancer-api-internal: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 5.374174ms
      message: 'load-balancer-api-internal: tcp connection to aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:05Z"
    - latency: 10.576591ms
      message: 'load-balancer-api-internal: resolved host name aee7651d5d000449ab33f7d6df782b9b-c05185c29a6a55a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:34:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T21:08:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-ip-10-0-131-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: 213d91dc-3715-4e24-9132-ee5efc2212d8
    resourceVersion: "25745"
    uid: 8e156599-015b-488e-abcf-f6f01d2df6bb
  spec:
    sourcePod: network-check-source-7d88cb55d8-sbdd7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:15:05Z"
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.206199ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 1.036638ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 1.66219ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:05Z"
    - latency: 1.008538ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:33:05Z"
    - latency: 851.618µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:32:05Z"
    - latency: 761.627µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:31:05Z"
    - latency: 816.937µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:30:05Z"
    - latency: 866.449µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:29:05Z"
    - latency: 878.626µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:28:05Z"
    - latency: 914.652µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T21:08:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-ip-10-0-134-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: 213d91dc-3715-4e24-9132-ee5efc2212d8
    resourceVersion: "25746"
    uid: e83c0752-f206-4003-809f-5af9bfd4caec
  spec:
    sourcePod: network-check-source-7d88cb55d8-sbdd7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:15:05Z"
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.985416ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 2.04733ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 2.343154ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:05Z"
    - latency: 2.017373ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:33:05Z"
    - latency: 2.133688ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:32:05Z"
    - latency: 1.694075ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:31:05Z"
    - latency: 2.211252ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:30:05Z"
    - latency: 2.1716ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:29:05Z"
    - latency: 2.306505ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:28:05Z"
    - latency: 1.788878ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T21:08:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-ip-10-0-139-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: 213d91dc-3715-4e24-9132-ee5efc2212d8
    resourceVersion: "25747"
    uid: 5895b2f4-91cc-4d5b-bdbb-dc3408da584a
  spec:
    sourcePod: network-check-source-7d88cb55d8-sbdd7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:15:05Z"
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.020557ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 1.757244ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 1.97198ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:05Z"
    - latency: 2.0309ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:33:05Z"
    - latency: 1.940761ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:32:05Z"
    - latency: 1.697024ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:31:05Z"
    - latency: 2.028407ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:30:05Z"
    - latency: 2.055007ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:29:05Z"
    - latency: 2.074554ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:28:05Z"
    - latency: 1.883643ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T21:08:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: 213d91dc-3715-4e24-9132-ee5efc2212d8
    resourceVersion: "26794"
    uid: a2cde394-265f-49e8-9884-695e8c11912b
  spec:
    sourcePod: network-check-source-7d88cb55d8-sbdd7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:14:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.278431ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:05Z"
    - latency: 1.625662ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:38:05Z"
    - latency: 997.19µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:05Z"
    - latency: 1.789893ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:37:05Z"
    - latency: 867.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 2.103509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:36:05Z"
    - latency: 799.362µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 1.972354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:35:05Z"
    - latency: 1.046134ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:05Z"
    - latency: 1.72286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:34:05Z"
kind: List
metadata:
  resourceVersion: ""