apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-83-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-83.ec2.internal
      uid: 5ce2b868-27ff-4740-92eb-d684678ee173
    resourceVersion: "61549"
    uid: 5f196945-c77f-4f04-a253-01a62a1a6dbd
  spec:
    sourcePod: network-check-source-869dcfcdcd-xjq8k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:39:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.086279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 943.546µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 920.923µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 959.185µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 1.058385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:08Z"
    - latency: 1.040423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:08Z"
    - latency: 1.767308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:08Z"
    - latency: 1.008332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:08Z"
    - latency: 1.124848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:08Z"
    - latency: 1.722348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-83-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-83.ec2.internal
      uid: 5ce2b868-27ff-4740-92eb-d684678ee173
    resourceVersion: "61551"
    uid: 9369d5b8-45f5-4380-b25c-b4b8d8d5f139
  spec:
    sourcePod: network-check-source-869dcfcdcd-xjq8k
    targetEndpoint: abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:38:08Z"
      message: 'load-balancer-api-external: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.947962ms
      message: 'load-balancer-api-external: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 9.502715ms
      message: 'load-balancer-api-external: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 4.9719ms
      message: 'load-balancer-api-external: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 8.642055ms
      message: 'load-balancer-api-external: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 4.576128ms
      message: 'load-balancer-api-external: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 10.774274ms
      message: 'load-balancer-api-external: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 4.408415ms
      message: 'load-balancer-api-external: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 10.735376ms
      message: 'load-balancer-api-external: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 5.262422ms
      message: 'load-balancer-api-external: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:08Z"
    - latency: 9.370985ms
      message: 'load-balancer-api-external: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:10:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-83-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-83.ec2.internal
      uid: 5ce2b868-27ff-4740-92eb-d684678ee173
    resourceVersion: "61550"
    uid: e7e45449-7bb2-4c2a-90c0-c5f4e657189e
  spec:
    sourcePod: network-check-source-869dcfcdcd-xjq8k
    targetEndpoint: abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:38:08Z"
      message: 'load-balancer-api-internal: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.907836ms
      message: 'load-balancer-api-internal: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 9.477317ms
      message: 'load-balancer-api-internal: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 4.703905ms
      message: 'load-balancer-api-internal: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 8.574207ms
      message: 'load-balancer-api-internal: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 6.130198ms
      message: 'load-balancer-api-internal: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 10.832394ms
      message: 'load-balancer-api-internal: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 4.457945ms
      message: 'load-balancer-api-internal: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 10.710963ms
      message: 'load-balancer-api-internal: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 5.241284ms
      message: 'load-balancer-api-internal: tcp connection to abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:08Z"
    - latency: 9.382488ms
      message: 'load-balancer-api-internal: resolved host name abd198e9e2bce4b048cb48001118d3a4-e42031d288e5c15c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:10:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-83-to-network-check-target-ip-10-0-134-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-83.ec2.internal
      uid: 5ce2b868-27ff-4740-92eb-d684678ee173
    resourceVersion: "61547"
    uid: fa077e00-32fb-46d9-8f62-35a5e5130fd5
  spec:
    sourcePod: network-check-source-869dcfcdcd-xjq8k
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:39:08Z"
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.576507ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 2.289738ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 2.381907ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 2.187389ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 1.999278ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:08Z"
    - latency: 1.967143ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:08Z"
    - latency: 2.087614ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:08Z"
    - latency: 1.955522ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:08Z"
    - latency: 2.210049ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:08Z"
    - latency: 1.952312ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-83-to-network-check-target-ip-10-0-135-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-83.ec2.internal
      uid: 5ce2b868-27ff-4740-92eb-d684678ee173
    resourceVersion: "61545"
    uid: 5bd62a20-fdaa-4d43-a3ef-96c9b6de67e5
  spec:
    sourcePod: network-check-source-869dcfcdcd-xjq8k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:39:08Z"
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.027732ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 1.634606ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 1.038133ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 1.126676ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 1.34053ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:08Z"
    - latency: 1.010091ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:08Z"
    - latency: 1.026831ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:08Z"
    - latency: 1.571265ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:08Z"
    - latency: 994.269µs
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:08Z"
    - latency: 1.009737ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-83-to-network-check-target-ip-10-0-143-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-83.ec2.internal
      uid: 5ce2b868-27ff-4740-92eb-d684678ee173
    resourceVersion: "61546"
    uid: 51b8d0c7-78fc-4bd3-9ea0-3d28f7e9f3c9
  spec:
    sourcePod: network-check-source-869dcfcdcd-xjq8k
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:39:08Z"
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.417253ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 2.318754ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 3.374654ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 3.005794ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 2.263425ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:08Z"
    - latency: 2.457096ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:08Z"
    - latency: 2.649411ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:08Z"
    - latency: 2.353982ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:08Z"
    - latency: 2.59717ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:08Z"
    - latency: 2.465312ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-83-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-83.ec2.internal
      uid: 5ce2b868-27ff-4740-92eb-d684678ee173
    resourceVersion: "61548"
    uid: 43e552a3-f5bb-4949-b6eb-044ec42e96e9
  spec:
    sourcePod: network-check-source-869dcfcdcd-xjq8k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:38:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.178848ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 2.294635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:14:08Z"
    - latency: 1.302748ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 1.814379ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:13:08Z"
    - latency: 990.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 1.732235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:12:08Z"
    - latency: 832.941µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 1.636125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:11:08Z"
    - latency: 1.169223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:08Z"
    - latency: 1.972489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:10:08Z"
kind: List
metadata:
  resourceVersion: ""