apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-82.ec2.internal
      uid: a7a05fd8-d2bd-4c61-8bae-f050067cded8
    resourceVersion: "73533"
    uid: 66cc426c-7a55-41f3-9d04-225e24df2763
  spec:
    sourcePod: network-check-source-869dcfcdcd-7dm27
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.211898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 1.612258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 1.144344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:42Z"
    - latency: 1.126273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:14:42Z"
    - latency: 1.901774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:13:42Z"
    - latency: 1.553009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:12:42Z"
    - latency: 1.262907ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:11:42Z"
    - latency: 1.184073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:10:42Z"
    - latency: 1.345651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:09:42Z"
    - latency: 1.044615ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:08:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-82.ec2.internal
      uid: a7a05fd8-d2bd-4c61-8bae-f050067cded8
    resourceVersion: "74739"
    uid: 5da827c5-34be-49c2-be4f-cda86b4cfa73
  spec:
    sourcePod: network-check-source-869dcfcdcd-7dm27
    targetEndpoint: acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:13:42Z"
      message: 'load-balancer-api-external: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.590359ms
      message: 'load-balancer-api-external: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:42Z"
    - latency: 15.405047ms
      message: 'load-balancer-api-external: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:19:42Z"
    - latency: 6.045724ms
      message: 'load-balancer-api-external: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:42Z"
    - latency: 8.619192ms
      message: 'load-balancer-api-external: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:18:42Z"
    - latency: 4.819809ms
      message: 'load-balancer-api-external: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 8.315588ms
      message: 'load-balancer-api-external: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 4.820012ms
      message: 'load-balancer-api-external: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 9.529053ms
      message: 'load-balancer-api-external: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 3.993123ms
      message: 'load-balancer-api-external: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:42Z"
    - latency: 10.753457ms
      message: 'load-balancer-api-external: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:15:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-82.ec2.internal
      uid: a7a05fd8-d2bd-4c61-8bae-f050067cded8
    resourceVersion: "74740"
    uid: 8b643185-5f51-44a6-85fa-bb720c36b6bb
  spec:
    sourcePod: network-check-source-869dcfcdcd-7dm27
    targetEndpoint: acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:13:42Z"
      message: 'load-balancer-api-internal: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.555337ms
      message: 'load-balancer-api-internal: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:42Z"
    - latency: 15.489145ms
      message: 'load-balancer-api-internal: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:19:42Z"
    - latency: 5.476932ms
      message: 'load-balancer-api-internal: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:42Z"
    - latency: 8.686765ms
      message: 'load-balancer-api-internal: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:18:42Z"
    - latency: 4.776495ms
      message: 'load-balancer-api-internal: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 8.391318ms
      message: 'load-balancer-api-internal: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 4.784771ms
      message: 'load-balancer-api-internal: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 9.563398ms
      message: 'load-balancer-api-internal: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 3.855033ms
      message: 'load-balancer-api-internal: tcp connection to acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:42Z"
    - latency: 10.781966ms
      message: 'load-balancer-api-internal: resolved host name acedd55ad419b4b75b7beb4cbae0c7a2-ffb7c518e1932034.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:15:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-82-to-network-check-target-ip-10-0-140-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-82.ec2.internal
      uid: a7a05fd8-d2bd-4c61-8bae-f050067cded8
    resourceVersion: "73531"
    uid: d6c5f631-2638-4743-9e7a-e7d49582abd5
  spec:
    sourcePod: network-check-source-869dcfcdcd-7dm27
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:42Z"
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.118687ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 2.09909ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 1.877617ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:42Z"
    - latency: 1.922292ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:14:42Z"
    - latency: 3.188759ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:13:42Z"
    - latency: 2.19382ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:12:42Z"
    - latency: 2.164524ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:11:42Z"
    - latency: 2.173376ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:10:42Z"
    - latency: 2.051749ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:09:42Z"
    - latency: 2.228102ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:08:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-82-to-network-check-target-ip-10-0-141-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-82.ec2.internal
      uid: a7a05fd8-d2bd-4c61-8bae-f050067cded8
    resourceVersion: "73530"
    uid: 986b533d-9e26-4ef0-9366-6b41817f826a
  spec:
    sourcePod: network-check-source-869dcfcdcd-7dm27
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:42Z"
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109513ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 1.086744ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 1.093574ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:42Z"
    - latency: 1.409535ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:14:42Z"
    - latency: 1.455745ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:13:42Z"
    - latency: 994.424µs
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:12:42Z"
    - latency: 1.691064ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:11:42Z"
    - latency: 957.618µs
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:10:42Z"
    - latency: 1.010867ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:09:42Z"
    - latency: 1.137084ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:08:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-82-to-network-check-target-ip-10-0-143-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-82.ec2.internal
      uid: a7a05fd8-d2bd-4c61-8bae-f050067cded8
    resourceVersion: "73532"
    uid: 224272ae-2b93-466f-89bf-4a903f4d1a3d
  spec:
    sourcePod: network-check-source-869dcfcdcd-7dm27
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:42Z"
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.492274ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 2.562894ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 1.911279ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:42Z"
    - latency: 2.119616ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:14:42Z"
    - latency: 2.275311ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:13:42Z"
    - latency: 2.148393ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:12:42Z"
    - latency: 2.431248ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:11:42Z"
    - latency: 2.150566ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:10:42Z"
    - latency: 2.188611ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:09:42Z"
    - latency: 2.295036ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:08:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-82.ec2.internal
      uid: a7a05fd8-d2bd-4c61-8bae-f050067cded8
    resourceVersion: "74737"
    uid: a6736ad3-0e2a-4562-809e-5d664300a68e
  spec:
    sourcePod: network-check-source-869dcfcdcd-7dm27
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:13:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.199933ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:42Z"
    - latency: 1.811782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:19:42Z"
    - latency: 846.438µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:42Z"
    - latency: 2.040133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:18:42Z"
    - latency: 1.279905ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 2.051218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:17:42Z"
    - latency: 1.049426ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 2.611959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:16:42Z"
    - latency: 892.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:42Z"
    - latency: 1.888602ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:15:42Z"
kind: List
metadata:
  resourceVersion: ""