apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T16:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 4e077cbf-a7c2-4b61-90b2-e6425b6994cd
    resourceVersion: "54880"
    uid: 27cd68c4-3e56-4ac1-8fdd-337433ec2d6d
  spec:
    sourcePod: network-check-source-869dcfcdcd-xbwhp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:00: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.172148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 922.902µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 1.300933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 1.588756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:25:36Z"
    - latency: 1.129454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:24:36Z"
    - latency: 1.305967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:23:36Z"
    - latency: 966.692µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:22:36Z"
    - latency: 1.074275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:21:36Z"
    - latency: 1.118269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:20:36Z"
    - latency: 971.486µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:19:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T16:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 4e077cbf-a7c2-4b61-90b2-e6425b6994cd
    resourceVersion: "55810"
    uid: 50336b6f-3a34-4d6e-9687-76f504ff11f9
  spec:
    sourcePod: network-check-source-869dcfcdcd-xbwhp
    targetEndpoint: acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T16:59:36Z"
      message: 'load-balancer-api-external: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.054625ms
      message: 'load-balancer-api-external: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:29:36Z"
    - latency: 6.799623ms
      message: 'load-balancer-api-external: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:29:36Z"
    - latency: 4.716655ms
      message: 'load-balancer-api-external: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 7.91502ms
      message: 'load-balancer-api-external: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 4.874399ms
      message: 'load-balancer-api-external: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 7.138379ms
      message: 'load-balancer-api-external: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 3.801161ms
      message: 'load-balancer-api-external: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 7.429445ms
      message: 'load-balancer-api-external: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 4.84662ms
      message: 'load-balancer-api-external: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:25:36Z"
    - latency: 10.324137ms
      message: 'load-balancer-api-external: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:25:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T16:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 4e077cbf-a7c2-4b61-90b2-e6425b6994cd
    resourceVersion: "55809"
    uid: 47822253-01b7-4fd3-96f7-7b175507ca4d
  spec:
    sourcePod: network-check-source-869dcfcdcd-xbwhp
    targetEndpoint: acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T16:59:36Z"
      message: 'load-balancer-api-internal: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.137177ms
      message: 'load-balancer-api-internal: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:29:36Z"
    - latency: 6.773653ms
      message: 'load-balancer-api-internal: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:29:36Z"
    - latency: 4.365293ms
      message: 'load-balancer-api-internal: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 7.837595ms
      message: 'load-balancer-api-internal: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 5.317754ms
      message: 'load-balancer-api-internal: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 7.158729ms
      message: 'load-balancer-api-internal: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 3.148237ms
      message: 'load-balancer-api-internal: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 7.395157ms
      message: 'load-balancer-api-internal: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 3.858302ms
      message: 'load-balancer-api-internal: tcp connection to acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:25:36Z"
    - latency: 10.287444ms
      message: 'load-balancer-api-internal: resolved host name acac10ec78bd6449b8d63c3cee234a68-a763b2fe0e8ba2ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:25:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T16:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-128-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 4e077cbf-a7c2-4b61-90b2-e6425b6994cd
    resourceVersion: "54879"
    uid: 4dd4fdd3-1c49-4e78-a9be-951da248c550
  spec:
    sourcePod: network-check-source-869dcfcdcd-xbwhp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:00:36Z"
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.326188ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 2.323544ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 2.671544ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 2.899472ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:25:36Z"
    - latency: 2.073104ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:24:36Z"
    - latency: 2.25299ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:23:36Z"
    - latency: 2.419866ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:22:36Z"
    - latency: 2.192316ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:21:36Z"
    - latency: 2.493358ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:20:36Z"
    - latency: 2.347039ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:19:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T16:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-128-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 4e077cbf-a7c2-4b61-90b2-e6425b6994cd
    resourceVersion: "54878"
    uid: f256a264-2f52-40bc-bfc8-9d8656b7af5b
  spec:
    sourcePod: network-check-source-869dcfcdcd-xbwhp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:00:36Z"
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.981105ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 2.248188ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 2.251282ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 2.407052ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:25:36Z"
    - latency: 2.381106ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:24:36Z"
    - latency: 2.292184ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:23:36Z"
    - latency: 2.362427ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:22:36Z"
    - latency: 2.553087ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:21:36Z"
    - latency: 2.426443ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:20:36Z"
    - latency: 2.206051ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:19:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T16:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-132-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 4e077cbf-a7c2-4b61-90b2-e6425b6994cd
    resourceVersion: "54877"
    uid: 704ebd99-b55d-4a7e-b043-996cc0d1a1fd
  spec:
    sourcePod: network-check-source-869dcfcdcd-xbwhp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:00:36Z"
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.915µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 1.219123ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 855.013µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 1.329078ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:25:36Z"
    - latency: 1.042722ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:24:36Z"
    - latency: 1.201426ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:23:36Z"
    - latency: 1.026762ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:22:36Z"
    - latency: 1.218375ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:21:36Z"
    - latency: 1.008917ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:20:36Z"
    - latency: 960.593µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:19:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T16:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 4e077cbf-a7c2-4b61-90b2-e6425b6994cd
    resourceVersion: "55808"
    uid: d0c38dd9-b914-4506-af06-4cb0eca1d00e
  spec:
    sourcePod: network-check-source-869dcfcdcd-xbwhp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T16:59:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 853.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:29:36Z"
    - latency: 1.7863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:29:36Z"
    - latency: 1.081804ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 1.857805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:28:36Z"
    - latency: 1.394518ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 1.853492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:27:36Z"
    - latency: 1.115659ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 1.891173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:26:36Z"
    - latency: 981.589µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T17:25:36Z"
    - latency: 2.068463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T17:25:36Z"
kind: List
metadata:
  resourceVersion: ""