apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: 841e4f1e-89a3-4cdd-a82a-8647401c0621
    resourceVersion: "53358"
    uid: 099d7df3-b5fb-492b-9bd5-7a2ee849ec85
  spec:
    sourcePod: network-check-source-989f8b8dc-rstrk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:29:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 1.038468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 1.076605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 1.107361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:26Z"
    - latency: 1.04825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:26Z"
    - latency: 1.163149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:26Z"
    - latency: 1.345316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:26Z"
    - latency: 1.028018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:26Z"
    - latency: 1.105326ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:26Z"
    - latency: 1.495201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: 841e4f1e-89a3-4cdd-a82a-8647401c0621
    resourceVersion: "54350"
    uid: 31a5e831-56c0-463a-9367-6af1a519d630
  spec:
    sourcePod: network-check-source-989f8b8dc-rstrk
    targetEndpoint: aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:28:26Z"
      message: 'load-balancer-api-external: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.932453ms
      message: 'load-balancer-api-external: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:58:26Z"
    - latency: 8.344946ms
      message: 'load-balancer-api-external: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:58:26Z"
    - latency: 3.299576ms
      message: 'load-balancer-api-external: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 8.736669ms
      message: 'load-balancer-api-external: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 4.075335ms
      message: 'load-balancer-api-external: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 8.213024ms
      message: 'load-balancer-api-external: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 7.196198ms
      message: 'load-balancer-api-external: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 9.0723ms
      message: 'load-balancer-api-external: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 4.888772ms
      message: 'load-balancer-api-external: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:26Z"
    - latency: 10.196909ms
      message: 'load-balancer-api-external: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:54:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: 841e4f1e-89a3-4cdd-a82a-8647401c0621
    resourceVersion: "54349"
    uid: b98aecbd-2b1d-4090-8ae8-708c9589a582
  spec:
    sourcePod: network-check-source-989f8b8dc-rstrk
    targetEndpoint: aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:28:26Z"
      message: 'load-balancer-api-internal: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.508196ms
      message: 'load-balancer-api-internal: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:58:26Z"
    - latency: 8.315552ms
      message: 'load-balancer-api-internal: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:58:26Z"
    - latency: 3.051614ms
      message: 'load-balancer-api-internal: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 8.656801ms
      message: 'load-balancer-api-internal: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 4.131077ms
      message: 'load-balancer-api-internal: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 8.074273ms
      message: 'load-balancer-api-internal: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 5.871412ms
      message: 'load-balancer-api-internal: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 8.925736ms
      message: 'load-balancer-api-internal: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 4.972662ms
      message: 'load-balancer-api-internal: tcp connection to aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:26Z"
    - latency: 10.157184ms
      message: 'load-balancer-api-internal: resolved host name aec81392bdba44bd1ab8512d22883f90-ac231e70f00c7a02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:54:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-128-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: 841e4f1e-89a3-4cdd-a82a-8647401c0621
    resourceVersion: "53356"
    uid: 8c76f43e-dc7c-4473-8d5e-ad9bff9ae856
  spec:
    sourcePod: network-check-source-989f8b8dc-rstrk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:29:26Z"
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42693ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 2.176595ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 2.093439ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 2.380129ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:26Z"
    - latency: 2.469821ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:26Z"
    - latency: 2.54197ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:26Z"
    - latency: 2.305692ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:26Z"
    - latency: 2.399245ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:26Z"
    - latency: 2.750561ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:26Z"
    - latency: 2.382598ms
      message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-132-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: 841e4f1e-89a3-4cdd-a82a-8647401c0621
    resourceVersion: "53355"
    uid: 47682902-ee45-4a7e-a9de-33f2d82dfa64
  spec:
    sourcePod: network-check-source-989f8b8dc-rstrk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:29:26Z"
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.881µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 1.029061ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 1.114602ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 1.08108ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:26Z"
    - latency: 1.205226ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:26Z"
    - latency: 1.028761ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:26Z"
    - latency: 915.029µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:26Z"
    - latency: 1.078211ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:26Z"
    - latency: 1.426093ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:26Z"
    - latency: 936.42µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-141-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: 841e4f1e-89a3-4cdd-a82a-8647401c0621
    resourceVersion: "53357"
    uid: 51767f23-6ad1-4955-a893-ff0d8b70cdcc
  spec:
    sourcePod: network-check-source-989f8b8dc-rstrk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:29:26Z"
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.36643ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 2.166066ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 2.451067ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 2.257449ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:26Z"
    - latency: 2.048079ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:26Z"
    - latency: 2.33136ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:26Z"
    - latency: 2.248735ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:26Z"
    - latency: 2.454043ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:26Z"
    - latency: 2.675262ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:26Z"
    - latency: 2.271864ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: 841e4f1e-89a3-4cdd-a82a-8647401c0621
    resourceVersion: "54348"
    uid: 720b891a-3c07-43fc-8161-4342c1a18d91
  spec:
    sourcePod: network-check-source-989f8b8dc-rstrk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:28:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014264ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:58:26Z"
    - latency: 1.740076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:58:26Z"
    - latency: 844.434µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 1.762692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:57:26Z"
    - latency: 830.181µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 1.833512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:56:26Z"
    - latency: 890.175µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 1.770026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:55:26Z"
    - latency: 854.915µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:26Z"
    - latency: 1.800445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:54:26Z"
kind: List
metadata:
  resourceVersion: ""