apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:51:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-251-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-251.ec2.internal
      uid: 6a2a3a1d-ea8b-4b0c-bc31-616bc584ae70
    resourceVersion: "30835"
    uid: 32dafbf8-4bc8-4990-ab65-ce6854f6a785
  spec:
    sourcePod: network-check-source-56d84b9f44-rjzvr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:58:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.725µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:05:42Z"
    - latency: 769.224µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:04:42Z"
    - latency: 1.404554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 930.581µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 862.13µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 927.72µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 3.125932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:59:42Z"
    - latency: 1.546439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:58:42Z"
    - latency: 1.058946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:57:42Z"
    - latency: 890.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:56:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:51:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-251-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-251.ec2.internal
      uid: 6a2a3a1d-ea8b-4b0c-bc31-616bc584ae70
    resourceVersion: "29265"
    uid: 0b6c1204-9370-4209-be7c-f61200872cea
  spec:
    sourcePod: network-check-source-56d84b9f44-rjzvr
    targetEndpoint: a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:57:42Z"
      message: 'load-balancer-api-external: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.352938ms
      message: 'load-balancer-api-external: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 6.669704ms
      message: 'load-balancer-api-external: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 4.632167ms
      message: 'load-balancer-api-external: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 6.883152ms
      message: 'load-balancer-api-external: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 5.244643ms
      message: 'load-balancer-api-external: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 7.191675ms
      message: 'load-balancer-api-external: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 5.900087ms
      message: 'load-balancer-api-external: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 7.442499ms
      message: 'load-balancer-api-external: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 5.527041ms
      message: 'load-balancer-api-external: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:59:42Z"
    - latency: 8.471078ms
      message: 'load-balancer-api-external: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:59:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:51:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-251-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-251.ec2.internal
      uid: 6a2a3a1d-ea8b-4b0c-bc31-616bc584ae70
    resourceVersion: "29266"
    uid: 8ef0352d-5a83-40b6-844d-2e93d68b0e4f
  spec:
    sourcePod: network-check-source-56d84b9f44-rjzvr
    targetEndpoint: a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:57:42Z"
      message: 'load-balancer-api-internal: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.317553ms
      message: 'load-balancer-api-internal: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 6.697288ms
      message: 'load-balancer-api-internal: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 4.648072ms
      message: 'load-balancer-api-internal: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 6.768254ms
      message: 'load-balancer-api-internal: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 5.214339ms
      message: 'load-balancer-api-internal: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 7.136189ms
      message: 'load-balancer-api-internal: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 5.813873ms
      message: 'load-balancer-api-internal: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 7.532561ms
      message: 'load-balancer-api-internal: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 5.547787ms
      message: 'load-balancer-api-internal: tcp connection to a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:59:42Z"
    - latency: 8.405633ms
      message: 'load-balancer-api-internal: resolved host name a7f6468b2798e469e8787521613d8bf0-2c555d2f161c09ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:59:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:51:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-251-to-network-check-target-ip-10-0-136-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-251.ec2.internal
      uid: 6a2a3a1d-ea8b-4b0c-bc31-616bc584ae70
    resourceVersion: "30832"
    uid: c90ae610-6725-4553-bdc5-b5ff1a4188c9
  spec:
    sourcePod: network-check-source-56d84b9f44-rjzvr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:58:42Z"
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.047917ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:05:42Z"
    - latency: 1.300534ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:04:42Z"
    - latency: 965.929µs
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 843.955µs
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 1.488892ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 1.075663ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 3.452174ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:59:42Z"
    - latency: 1.305303ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:58:42Z"
    - latency: 869.434µs
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:57:42Z"
    - latency: 903.404µs
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:56:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:51:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-251-to-network-check-target-ip-10-0-141-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-251.ec2.internal
      uid: 6a2a3a1d-ea8b-4b0c-bc31-616bc584ae70
    resourceVersion: "30833"
    uid: 867c0804-f4b5-4a3c-a321-6d22e417a022
  spec:
    sourcePod: network-check-source-56d84b9f44-rjzvr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:58:42Z"
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.107935ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:05:42Z"
    - latency: 2.031992ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:04:42Z"
    - latency: 1.983397ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 2.453133ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 2.177493ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 2.183051ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 2.252371ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:59:42Z"
    - latency: 2.267092ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:58:42Z"
    - latency: 2.130444ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:57:42Z"
    - latency: 1.955681ms
      message: 'network-check-target-ip-10-0-141-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:56:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:51:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-251-to-network-check-target-ip-10-0-143-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-251.ec2.internal
      uid: 6a2a3a1d-ea8b-4b0c-bc31-616bc584ae70
    resourceVersion: "30834"
    uid: b9516c3b-8ddb-46ff-a14e-49be69482028
  spec:
    sourcePod: network-check-source-56d84b9f44-rjzvr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:58:42Z"
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.890325ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:05:42Z"
    - latency: 1.926225ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:04:42Z"
    - latency: 1.79611ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 1.887014ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 2.14485ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 2.047853ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 2.107597ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:59:42Z"
    - latency: 2.57087ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:58:42Z"
    - latency: 1.886487ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:57:42Z"
    - latency: 1.591662ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:56:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:51:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-251-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-251.ec2.internal
      uid: 6a2a3a1d-ea8b-4b0c-bc31-616bc584ae70
    resourceVersion: "29263"
    uid: 7fcc7716-962e-4da3-a455-9577da551e94
  spec:
    sourcePod: network-check-source-56d84b9f44-rjzvr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:57:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 664.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 1.881507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:03:42Z"
    - latency: 820.07µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 1.763232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:02:42Z"
    - latency: 793.88µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 1.892209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:01:42Z"
    - latency: 827.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 2.062349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:00:42Z"
    - latency: 1.130084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:59:42Z"
    - latency: 3.075869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:59:42Z"
kind: List
metadata:
  resourceVersion: ""