apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:05:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-80-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-80.ec2.internal
      uid: c6509144-7d7e-4fb5-aa51-9c7ae5f52d5a
    resourceVersion: "23256"
    uid: c6e19a72-6346-411d-9f41-7e99d45943c1
  spec:
    sourcePod: network-check-source-685456655f-j9hqj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:12:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.755237ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 1.090434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 1.125243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:57Z"
    - latency: 1.072045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:57Z"
    - latency: 941.995µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:57Z"
    - latency: 971.286µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:57Z"
    - latency: 960.101µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:57Z"
    - latency: 827.338µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:57Z"
    - latency: 1.405829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:57Z"
    - latency: 967.277µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:05:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-80-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-80.ec2.internal
      uid: c6509144-7d7e-4fb5-aa51-9c7ae5f52d5a
    resourceVersion: "24103"
    uid: 1d5645c2-b599-4b69-8c0f-cacc236fbf32
  spec:
    sourcePod: network-check-source-685456655f-j9hqj
    targetEndpoint: a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:11:57Z"
      message: 'load-balancer-api-external: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.617398ms
      message: 'load-balancer-api-external: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:35:57Z"
    - latency: 9.045639ms
      message: 'load-balancer-api-external: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:35:57Z"
    - latency: 5.412737ms
      message: 'load-balancer-api-external: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:57Z"
    - latency: 14.698891ms
      message: 'load-balancer-api-external: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:57Z"
    - latency: 5.389442ms
      message: 'load-balancer-api-external: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 8.401502ms
      message: 'load-balancer-api-external: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 4.957488ms
      message: 'load-balancer-api-external: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 8.24595ms
      message: 'load-balancer-api-external: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 5.519159ms
      message: 'load-balancer-api-external: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:57Z"
    - latency: 9.684707ms
      message: 'load-balancer-api-external: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:05:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-80-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-80.ec2.internal
      uid: c6509144-7d7e-4fb5-aa51-9c7ae5f52d5a
    resourceVersion: "24104"
    uid: 1c4cf880-3de6-4f05-bf5a-6acfff84de21
  spec:
    sourcePod: network-check-source-685456655f-j9hqj
    targetEndpoint: a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:11:57Z"
      message: 'load-balancer-api-internal: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.360345ms
      message: 'load-balancer-api-internal: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:35:57Z"
    - latency: 9.182462ms
      message: 'load-balancer-api-internal: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:35:57Z"
    - latency: 4.995409ms
      message: 'load-balancer-api-internal: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:57Z"
    - latency: 14.674098ms
      message: 'load-balancer-api-internal: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:57Z"
    - latency: 7.000095ms
      message: 'load-balancer-api-internal: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 8.552194ms
      message: 'load-balancer-api-internal: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 4.942212ms
      message: 'load-balancer-api-internal: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 8.36625ms
      message: 'load-balancer-api-internal: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 6.648004ms
      message: 'load-balancer-api-internal: tcp connection to a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:57Z"
    - latency: 9.774196ms
      message: 'load-balancer-api-internal: resolved host name a642bfeefa8a9492ebe7af33e67e7fb0-059fa60265adea46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:05:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-80-to-network-check-target-ip-10-0-132-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-80.ec2.internal
      uid: c6509144-7d7e-4fb5-aa51-9c7ae5f52d5a
    resourceVersion: "23254"
    uid: 7c01f3ba-0262-4315-992f-69215b12a463
  spec:
    sourcePod: network-check-source-685456655f-j9hqj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:12:57Z"
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.099931ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 2.464169ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 2.054694ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:57Z"
    - latency: 2.388819ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:57Z"
    - latency: 2.50764ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:57Z"
    - latency: 2.30566ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:57Z"
    - latency: 2.099839ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:57Z"
    - latency: 2.182913ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:57Z"
    - latency: 2.379065ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:57Z"
    - latency: 2.267813ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:05:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-80-to-network-check-target-ip-10-0-138-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-80.ec2.internal
      uid: c6509144-7d7e-4fb5-aa51-9c7ae5f52d5a
    resourceVersion: "23253"
    uid: 351c953d-9a19-4c91-8fad-6307cc1a6f9a
  spec:
    sourcePod: network-check-source-685456655f-j9hqj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:12:57Z"
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.545707ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 5.593965ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 2.150242ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:57Z"
    - latency: 4.995884ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:57Z"
    - latency: 2.197346ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:57Z"
    - latency: 2.10616ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:57Z"
    - latency: 1.895454ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:57Z"
    - latency: 2.014643ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:57Z"
    - latency: 2.001777ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:57Z"
    - latency: 2.129462ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:05:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-80-to-network-check-target-ip-10-0-141-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-80.ec2.internal
      uid: c6509144-7d7e-4fb5-aa51-9c7ae5f52d5a
    resourceVersion: "23255"
    uid: 5bf6308b-9328-472c-ab24-e32ef2caf34b
  spec:
    sourcePod: network-check-source-685456655f-j9hqj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:12:57Z"
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 804.417µs
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 1.379129ms
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 946.506µs
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:57Z"
    - latency: 1.322676ms
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:57Z"
    - latency: 909.258µs
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:57Z"
    - latency: 1.043815ms
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:57Z"
    - latency: 849.723µs
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:57Z"
    - latency: 791.107µs
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:57Z"
    - latency: 838.277µs
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:57Z"
    - latency: 812.509µs
      message: 'network-check-target-ip-10-0-141-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:05:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-80-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-80.ec2.internal
      uid: c6509144-7d7e-4fb5-aa51-9c7ae5f52d5a
    resourceVersion: "24102"
    uid: 33af3004-ece2-4a15-9154-f4854074e747
  spec:
    sourcePod: network-check-source-685456655f-j9hqj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:11:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.218301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:35:57Z"
    - latency: 1.921475ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:35:57Z"
    - latency: 1.116665ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:57Z"
    - latency: 2.077247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:57Z"
    - latency: 1.126323ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 1.99452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:57Z"
    - latency: 909.413µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 1.824068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:57Z"
    - latency: 3.524163ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:57Z"
    - latency: 1.914657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:57Z"
kind: List
metadata:
  resourceVersion: ""