apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-255-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-255.ec2.internal
      uid: de2676c3-e8d3-43fc-a071-f4b2a31a9d7e
    resourceVersion: "63256"
    uid: d7ef5085-9ecb-45cd-8b27-552367a8cc57
  spec:
    sourcePod: network-check-source-7cbc45fddc-x45px
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:10:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 778.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 1.390193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 838.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 860.365µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:35:43Z"
    - latency: 1.074949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:34:43Z"
    - latency: 1.289766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:33:43Z"
    - latency: 1.262882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:32:43Z"
    - latency: 1.211273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:31:43Z"
    - latency: 1.453938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:30:43Z"
    - latency: 1.129095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:29:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-255-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-255.ec2.internal
      uid: de2676c3-e8d3-43fc-a071-f4b2a31a9d7e
    resourceVersion: "64097"
    uid: 9690cb26-0faf-4fd1-babe-8981e8b2c783
  spec:
    sourcePod: network-check-source-7cbc45fddc-x45px
    targetEndpoint: a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:09:43Z"
      message: 'load-balancer-api-external: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.321671ms
      message: 'load-balancer-api-external: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:39:43Z"
    - latency: 8.276985ms
      message: 'load-balancer-api-external: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:39:43Z"
    - latency: 5.904888ms
      message: 'load-balancer-api-external: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 7.754919ms
      message: 'load-balancer-api-external: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 14.577675ms
      message: 'load-balancer-api-external: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 6.397514ms
      message: 'load-balancer-api-external: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 4.811318ms
      message: 'load-balancer-api-external: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 7.611524ms
      message: 'load-balancer-api-external: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 4.989759ms
      message: 'load-balancer-api-external: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:35:43Z"
    - latency: 7.151311ms
      message: 'load-balancer-api-external: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:35:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-255-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-255.ec2.internal
      uid: de2676c3-e8d3-43fc-a071-f4b2a31a9d7e
    resourceVersion: "64096"
    uid: 306751e4-cb62-43eb-9002-ea309e4707d4
  spec:
    sourcePod: network-check-source-7cbc45fddc-x45px
    targetEndpoint: a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:09:43Z"
      message: 'load-balancer-api-internal: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.309107ms
      message: 'load-balancer-api-internal: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:39:43Z"
    - latency: 8.14593ms
      message: 'load-balancer-api-internal: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:39:43Z"
    - latency: 5.890886ms
      message: 'load-balancer-api-internal: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 7.624462ms
      message: 'load-balancer-api-internal: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 5.868818ms
      message: 'load-balancer-api-internal: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 6.424632ms
      message: 'load-balancer-api-internal: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 4.543817ms
      message: 'load-balancer-api-internal: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 7.530375ms
      message: 'load-balancer-api-internal: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 5.013898ms
      message: 'load-balancer-api-internal: tcp connection to a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:35:43Z"
    - latency: 7.060457ms
      message: 'load-balancer-api-internal: resolved host name a66ec91cf751f4c1382c481e2fb16083-c3d57fc087862a64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:35:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-255-to-network-check-target-ip-10-0-133-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-255.ec2.internal
      uid: de2676c3-e8d3-43fc-a071-f4b2a31a9d7e
    resourceVersion: "63255"
    uid: c70467ac-33b3-420e-aea1-31003f7373c7
  spec:
    sourcePod: network-check-source-7cbc45fddc-x45px
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:10:43Z"
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.078356ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 2.022154ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 2.304473ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 1.933977ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:35:43Z"
    - latency: 2.6682ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:34:43Z"
    - latency: 2.459717ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:33:43Z"
    - latency: 2.428707ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:32:43Z"
    - latency: 2.572868ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:31:43Z"
    - latency: 2.498657ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:30:43Z"
    - latency: 2.35241ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:29:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-255-to-network-check-target-ip-10-0-141-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-255.ec2.internal
      uid: de2676c3-e8d3-43fc-a071-f4b2a31a9d7e
    resourceVersion: "63253"
    uid: 18695798-670a-4b51-9d95-a0fa509c1518
  spec:
    sourcePod: network-check-source-7cbc45fddc-x45px
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:10:43Z"
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.536µs
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 916.019µs
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 1.443914ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 869.948µs
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:35:43Z"
    - latency: 1.507794ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:34:43Z"
    - latency: 996.798µs
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:33:43Z"
    - latency: 910.334µs
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:32:43Z"
    - latency: 1.291222ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:31:43Z"
    - latency: 1.625281ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:30:43Z"
    - latency: 1.567692ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:29:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-255-to-network-check-target-ip-10-0-141-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-255.ec2.internal
      uid: de2676c3-e8d3-43fc-a071-f4b2a31a9d7e
    resourceVersion: "63254"
    uid: 44ab40ce-c842-477c-84c4-f74579eb243a
  spec:
    sourcePod: network-check-source-7cbc45fddc-x45px
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:10:43Z"
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.020547ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 1.964639ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 2.512123ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 2.271166ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:35:43Z"
    - latency: 2.424809ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:34:43Z"
    - latency: 2.39171ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:33:43Z"
    - latency: 2.202683ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:32:43Z"
    - latency: 2.533886ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:31:43Z"
    - latency: 2.954497ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:30:43Z"
    - latency: 2.309203ms
      message: 'network-check-target-ip-10-0-141-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:29:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-255-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-255.ec2.internal
      uid: de2676c3-e8d3-43fc-a071-f4b2a31a9d7e
    resourceVersion: "64095"
    uid: d00c37c1-3d61-4eab-a694-ec3e7bee274f
  spec:
    sourcePod: network-check-source-7cbc45fddc-x45px
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:09:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.132638ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:39:43Z"
    - latency: 2.1913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:39:43Z"
    - latency: 1.072008ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 2.045695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:38:43Z"
    - latency: 1.164304ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 1.871798ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:37:43Z"
    - latency: 1.283962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 2.216014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:36:43Z"
    - latency: 995.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:35:43Z"
    - latency: 1.96385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:35:43Z"
kind: List
metadata:
  resourceVersion: ""