apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-227.ec2.internal
      uid: 83cfb267-49f5-4050-b646-541d901f4ec5
    resourceVersion: "19638"
    uid: 46872d33-bf8c-4744-a95d-836fb625383d
  spec:
    sourcePod: network-check-source-685456655f-pwm62
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:12:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.63µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 868.924µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:45Z"
    - latency: 985.724µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:45Z"
    - latency: 1.173585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:45Z"
    - latency: 928.518µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:45Z"
    - latency: 1.053128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:45Z"
    - latency: 1.055799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:45Z"
    - latency: 1.123106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:45Z"
    - latency: 1.09567ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:45Z"
    - latency: 1.416686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-227.ec2.internal
      uid: 83cfb267-49f5-4050-b646-541d901f4ec5
    resourceVersion: "20982"
    uid: f92e7a6d-55da-4173-8741-0386edb5c4ed
  spec:
    sourcePod: network-check-source-685456655f-pwm62
    targetEndpoint: ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:11:45Z"
      message: 'load-balancer-api-external: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 11.687461ms
      message: 'load-balancer-api-external: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:29:45Z"
    - latency: 9.522028ms
      message: 'load-balancer-api-external: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:29:45Z"
    - latency: 5.884656ms
      message: 'load-balancer-api-external: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:28:45Z"
    - latency: 9.447883ms
      message: 'load-balancer-api-external: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:28:45Z"
    - latency: 4.181307ms
      message: 'load-balancer-api-external: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:45Z"
    - latency: 27.753917ms
      message: 'load-balancer-api-external: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:45Z"
    - latency: 6.216964ms
      message: 'load-balancer-api-external: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 10.643339ms
      message: 'load-balancer-api-external: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 5.006911ms
      message: 'load-balancer-api-external: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:45Z"
    - latency: 7.870419ms
      message: 'load-balancer-api-external: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-227.ec2.internal
      uid: 83cfb267-49f5-4050-b646-541d901f4ec5
    resourceVersion: "20981"
    uid: 1296ced2-8303-4fff-a6d3-765bf8d25a4d
  spec:
    sourcePod: network-check-source-685456655f-pwm62
    targetEndpoint: ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:11:45Z"
      message: 'load-balancer-api-internal: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.990588ms
      message: 'load-balancer-api-internal: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:29:45Z"
    - latency: 9.405692ms
      message: 'load-balancer-api-internal: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:29:45Z"
    - latency: 5.886409ms
      message: 'load-balancer-api-internal: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:28:45Z"
    - latency: 9.383902ms
      message: 'load-balancer-api-internal: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:28:45Z"
    - latency: 4.762159ms
      message: 'load-balancer-api-internal: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:45Z"
    - latency: 23.738381ms
      message: 'load-balancer-api-internal: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:45Z"
    - latency: 4.985303ms
      message: 'load-balancer-api-internal: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 10.661868ms
      message: 'load-balancer-api-internal: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 5.642186ms
      message: 'load-balancer-api-internal: tcp connection to ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:45Z"
    - latency: 7.778351ms
      message: 'load-balancer-api-internal: resolved host name ad2b7d5879f124c97a625159e1c4c108-45a3589c2608bb15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-227-to-network-check-target-ip-10-0-137-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-227.ec2.internal
      uid: 83cfb267-49f5-4050-b646-541d901f4ec5
    resourceVersion: "19635"
    uid: bb7a9d9b-11d9-4228-9574-41f9b8e43b90
  spec:
    sourcePod: network-check-source-685456655f-pwm62
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:12:45Z"
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.86µs
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 1.35006ms
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:45Z"
    - latency: 1.307401ms
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:45Z"
    - latency: 988.292µs
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:45Z"
    - latency: 991.818µs
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:45Z"
    - latency: 1.132868ms
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:45Z"
    - latency: 1.487524ms
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:45Z"
    - latency: 966.818µs
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:45Z"
    - latency: 1.001143ms
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:45Z"
    - latency: 894.07µs
      message: 'network-check-target-ip-10-0-137-227: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-227-to-network-check-target-ip-10-0-139-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-227.ec2.internal
      uid: 83cfb267-49f5-4050-b646-541d901f4ec5
    resourceVersion: "19636"
    uid: 929746a9-ba71-4b49-a7f1-de086d20fd78
  spec:
    sourcePod: network-check-source-685456655f-pwm62
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:12:45Z"
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.519178ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 2.416142ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:45Z"
    - latency: 2.380592ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:45Z"
    - latency: 2.574544ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:45Z"
    - latency: 2.540856ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:45Z"
    - latency: 2.244386ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:45Z"
    - latency: 2.477446ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:45Z"
    - latency: 2.543267ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:45Z"
    - latency: 2.625712ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:45Z"
    - latency: 2.404586ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-227-to-network-check-target-ip-10-0-139-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-227.ec2.internal
      uid: 83cfb267-49f5-4050-b646-541d901f4ec5
    resourceVersion: "19637"
    uid: 0134337b-f68f-49d0-b235-f7b885a32b0d
  spec:
    sourcePod: network-check-source-685456655f-pwm62
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:12:45Z"
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.2977ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 2.356203ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:45Z"
    - latency: 2.44101ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:45Z"
    - latency: 2.369097ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:45Z"
    - latency: 2.259841ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:45Z"
    - latency: 2.127939ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:45Z"
    - latency: 1.991096ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:45Z"
    - latency: 2.122271ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:45Z"
    - latency: 2.535593ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:45Z"
    - latency: 2.318581ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-227.ec2.internal
      uid: 83cfb267-49f5-4050-b646-541d901f4ec5
    resourceVersion: "20980"
    uid: 5af1b0b4-3322-44ea-97ec-1cc3bb499029
  spec:
    sourcePod: network-check-source-685456655f-pwm62
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:11:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208613ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:29:45Z"
    - latency: 1.934949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:29:45Z"
    - latency: 995.027µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:28:45Z"
    - latency: 1.810026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:28:45Z"
    - latency: 1.749899ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:45Z"
    - latency: 3.832985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:45Z"
    - latency: 1.856751ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 2.07622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:45Z"
    - latency: 949.782µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:45Z"
    - latency: 1.783843ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:45Z"
kind: List
metadata:
  resourceVersion: ""