apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-32-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-32.ec2.internal
      uid: 08319435-3acf-4025-85f0-b2bae2663936
    resourceVersion: "24151"
    uid: 1da4747a-c977-4248-a60e-20a5346b8612
  spec:
    sourcePod: network-check-source-685456655f-kz974
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:10:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 1.001964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 1.017244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 1.066746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:35:37Z"
    - latency: 817.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:34:37Z"
    - latency: 1.034481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:33:37Z"
    - latency: 833.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:32:37Z"
    - latency: 897.101µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:31:37Z"
    - latency: 1.047671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:30:37Z"
    - latency: 1.304709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-32-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-32.ec2.internal
      uid: 08319435-3acf-4025-85f0-b2bae2663936
    resourceVersion: "24480"
    uid: 5fc8c5d1-66a9-4c1d-953f-c008cf8ff3b9
  spec:
    sourcePod: network-check-source-685456655f-kz974
    targetEndpoint: a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:09:37Z"
      message: 'load-balancer-api-external: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.831744ms
      message: 'load-balancer-api-external: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:39:37Z"
    - latency: 6.310226ms
      message: 'load-balancer-api-external: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:39:37Z"
    - latency: 5.764953ms
      message: 'load-balancer-api-external: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 6.459146ms
      message: 'load-balancer-api-external: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 3.905495ms
      message: 'load-balancer-api-external: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 6.386551ms
      message: 'load-balancer-api-external: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 5.083005ms
      message: 'load-balancer-api-external: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 7.413666ms
      message: 'load-balancer-api-external: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 3.566457ms
      message: 'load-balancer-api-external: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:35:37Z"
    - latency: 6.842649ms
      message: 'load-balancer-api-external: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:35:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-32-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-32.ec2.internal
      uid: 08319435-3acf-4025-85f0-b2bae2663936
    resourceVersion: "24479"
    uid: c258d88c-2739-4f0e-bae5-942305224e9d
  spec:
    sourcePod: network-check-source-685456655f-kz974
    targetEndpoint: a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:09:37Z"
      message: 'load-balancer-api-internal: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.394715ms
      message: 'load-balancer-api-internal: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:39:37Z"
    - latency: 6.271855ms
      message: 'load-balancer-api-internal: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:39:37Z"
    - latency: 2.776407ms
      message: 'load-balancer-api-internal: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 6.421326ms
      message: 'load-balancer-api-internal: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 3.897974ms
      message: 'load-balancer-api-internal: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 6.336461ms
      message: 'load-balancer-api-internal: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 5.231467ms
      message: 'load-balancer-api-internal: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 7.494109ms
      message: 'load-balancer-api-internal: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 4.804231ms
      message: 'load-balancer-api-internal: tcp connection to a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:35:37Z"
    - latency: 6.816273ms
      message: 'load-balancer-api-internal: resolved host name a011b7197820a468ab3b1d8ee3a63c67-24a129cd1bf1303f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:35:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-32-to-network-check-target-ip-10-0-132-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-32.ec2.internal
      uid: 08319435-3acf-4025-85f0-b2bae2663936
    resourceVersion: "24148"
    uid: 66784d03-4a60-4beb-819f-bb388c809d22
  spec:
    sourcePod: network-check-source-685456655f-kz974
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:10:37Z"
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.283164ms
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 808.181µs
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 809.78µs
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 887.062µs
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:35:37Z"
    - latency: 1.231505ms
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:34:37Z"
    - latency: 882.122µs
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:33:37Z"
    - latency: 913.776µs
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:32:37Z"
    - latency: 1.410278ms
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:31:37Z"
    - latency: 736.949µs
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:30:37Z"
    - latency: 781.887µs
      message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-32-to-network-check-target-ip-10-0-132-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-32.ec2.internal
      uid: 08319435-3acf-4025-85f0-b2bae2663936
    resourceVersion: "24149"
    uid: 04480658-b9de-4a93-b7d6-f9729a5fee1d
  spec:
    sourcePod: network-check-source-685456655f-kz974
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:10:37Z"
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.199874ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 2.215519ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 2.139905ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 2.017241ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:35:37Z"
    - latency: 1.950974ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:34:37Z"
    - latency: 2.368981ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:33:37Z"
    - latency: 1.947063ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:32:37Z"
    - latency: 2.217086ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:31:37Z"
    - latency: 1.830038ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:30:37Z"
    - latency: 2.011353ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-32-to-network-check-target-ip-10-0-138-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-32.ec2.internal
      uid: 08319435-3acf-4025-85f0-b2bae2663936
    resourceVersion: "24150"
    uid: dcb3d204-4ba5-4c27-8d89-f00bc0ca83e6
  spec:
    sourcePod: network-check-source-685456655f-kz974
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:10:37Z"
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.274466ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 2.299128ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 2.554494ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 2.065259ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:35:37Z"
    - latency: 2.100892ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:34:37Z"
    - latency: 2.254492ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:33:37Z"
    - latency: 2.301074ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:32:37Z"
    - latency: 2.663132ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:31:37Z"
    - latency: 1.982152ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:30:37Z"
    - latency: 2.379135ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-32-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-32.ec2.internal
      uid: 08319435-3acf-4025-85f0-b2bae2663936
    resourceVersion: "24478"
    uid: 591cdb30-2869-4aa1-a90f-afa00abc0fa7
  spec:
    sourcePod: network-check-source-685456655f-kz974
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:09:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:39:37Z"
    - latency: 1.824573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:39:37Z"
    - latency: 861.415µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 1.527831ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:38:37Z"
    - latency: 916.935µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 2.097842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:37:37Z"
    - latency: 867.325µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 1.871935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:36:37Z"
    - latency: 886.381µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:35:37Z"
    - latency: 1.660833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:35:37Z"
kind: List
metadata:
  resourceVersion: ""