apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.ec2.internal
      uid: 08f6b875-20ce-4b11-9e97-0bd4f5575f00
    resourceVersion: "53344"
    uid: 84e9cfbf-54da-41bb-b195-5ada20304d97
  spec:
    sourcePod: network-check-source-685456655f-m646p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.937168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 916.83µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 1.154659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:38:36Z"
    - latency: 1.041314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:37:36Z"
    - latency: 939.15µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:36:36Z"
    - latency: 1.251589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:35:36Z"
    - latency: 1.3093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:34:36Z"
    - latency: 1.316998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:33:36Z"
    - latency: 1.277255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:32:36Z"
    - latency: 1.057707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:31:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.ec2.internal
      uid: 08f6b875-20ce-4b11-9e97-0bd4f5575f00
    resourceVersion: "54798"
    uid: 70107d20-b8ab-49d5-bfc9-b368765e463b
  spec:
    sourcePod: network-check-source-685456655f-m646p
    targetEndpoint: a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:18:36Z"
      message: 'load-balancer-api-external: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.625332ms
      message: 'load-balancer-api-external: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:42:36Z"
    - latency: 8.151457ms
      message: 'load-balancer-api-external: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:42:36Z"
    - latency: 3.835078ms
      message: 'load-balancer-api-external: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:41:36Z"
    - latency: 7.961995ms
      message: 'load-balancer-api-external: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:41:36Z"
    - latency: 5.382955ms
      message: 'load-balancer-api-external: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 7.755138ms
      message: 'load-balancer-api-external: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 4.152657ms
      message: 'load-balancer-api-external: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 7.458691ms
      message: 'load-balancer-api-external: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 3.863726ms
      message: 'load-balancer-api-external: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:38:36Z"
    - latency: 6.967986ms
      message: 'load-balancer-api-external: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:38:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.ec2.internal
      uid: 08f6b875-20ce-4b11-9e97-0bd4f5575f00
    resourceVersion: "54799"
    uid: ea1d71fe-23b0-4eb1-bbda-9ae9dac8cfbe
  spec:
    sourcePod: network-check-source-685456655f-m646p
    targetEndpoint: a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:18:36Z"
      message: 'load-balancer-api-internal: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.604596ms
      message: 'load-balancer-api-internal: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:42:36Z"
    - latency: 8.204891ms
      message: 'load-balancer-api-internal: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:42:36Z"
    - latency: 3.845207ms
      message: 'load-balancer-api-internal: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:41:36Z"
    - latency: 8.009698ms
      message: 'load-balancer-api-internal: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:41:36Z"
    - latency: 4.014839ms
      message: 'load-balancer-api-internal: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 7.716116ms
      message: 'load-balancer-api-internal: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 4.396174ms
      message: 'load-balancer-api-internal: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 7.395028ms
      message: 'load-balancer-api-internal: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 3.854701ms
      message: 'load-balancer-api-internal: tcp connection to a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:38:36Z"
    - latency: 7.026391ms
      message: 'load-balancer-api-internal: resolved host name a97dc365a9d8740bebc562947ec51052-76cb69358fa3569a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:38:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-ip-10-0-129-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.ec2.internal
      uid: 08f6b875-20ce-4b11-9e97-0bd4f5575f00
    resourceVersion: "53341"
    uid: f70b73c4-034a-49e4-8339-5d41f4ca5a70
  spec:
    sourcePod: network-check-source-685456655f-m646p
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:36Z"
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.952497ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 1.942026ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 1.970529ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:38:36Z"
    - latency: 1.895519ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:37:36Z"
    - latency: 1.97484ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:36:36Z"
    - latency: 2.155794ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:35:36Z"
    - latency: 2.186196ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:34:36Z"
    - latency: 2.266074ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:33:36Z"
    - latency: 2.447043ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:32:36Z"
    - latency: 2.125558ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:31:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-ip-10-0-130-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.ec2.internal
      uid: 08f6b875-20ce-4b11-9e97-0bd4f5575f00
    resourceVersion: "53343"
    uid: 411e9dbf-cd7d-4ff4-a00e-3f686a10cf3e
  spec:
    sourcePod: network-check-source-685456655f-m646p
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:36Z"
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.053µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 944.197µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 911.797µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:38:36Z"
    - latency: 1.396954ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:37:36Z"
    - latency: 991.896µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:36:36Z"
    - latency: 863.223µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:35:36Z"
    - latency: 892.68µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:34:36Z"
    - latency: 1.183244ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:33:36Z"
    - latency: 1.034832ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:32:36Z"
    - latency: 1.095761ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:31:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-ip-10-0-139-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.ec2.internal
      uid: 08f6b875-20ce-4b11-9e97-0bd4f5575f00
    resourceVersion: "53342"
    uid: f40f4cc1-4f31-416f-b1c5-25d5f2e3cdf6
  spec:
    sourcePod: network-check-source-685456655f-m646p
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:36Z"
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.970338ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 1.821129ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 1.854007ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:38:36Z"
    - latency: 1.958376ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:37:36Z"
    - latency: 1.865424ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:36:36Z"
    - latency: 2.157631ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:35:36Z"
    - latency: 2.29642ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:34:36Z"
    - latency: 2.02573ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:33:36Z"
    - latency: 2.475105ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:32:36Z"
    - latency: 1.991043ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:31:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.ec2.internal
      uid: 08f6b875-20ce-4b11-9e97-0bd4f5575f00
    resourceVersion: "54797"
    uid: f63fd06f-5ded-4b92-b977-d2f6453f8256
  spec:
    sourcePod: network-check-source-685456655f-m646p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:18:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.674µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:42:36Z"
    - latency: 2.023461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:42:36Z"
    - latency: 993.348µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:41:36Z"
    - latency: 1.913438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:41:36Z"
    - latency: 828.068µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 2.225211ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:40:36Z"
    - latency: 993.508µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 2.109952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:39:36Z"
    - latency: 1.176696ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:38:36Z"
    - latency: 1.964882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:38:36Z"
kind: List
metadata:
  resourceVersion: ""