apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-249-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-249.ec2.internal
      uid: 3c7237c1-4ad0-4cd5-8e26-704dde9e6aa0
    resourceVersion: "42995"
    uid: 010dc52c-2e24-40b8-9787-424b11a1de51
  spec:
    sourcePod: network-check-source-8894fc9bd-4h869
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T15:05:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.011112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 912.527µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 951.617µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:24:40Z"
    - latency: 817.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:23:40Z"
    - latency: 1.382031ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:22:40Z"
    - latency: 1.14522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:21:40Z"
    - latency: 1.156449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:20:40Z"
    - latency: 1.110681ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:19:40Z"
    - latency: 873.411µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:18:40Z"
    - latency: 1.257279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:17:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-249-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-249.ec2.internal
      uid: 3c7237c1-4ad0-4cd5-8e26-704dde9e6aa0
    resourceVersion: "44700"
    uid: 28151762-ffa1-4ebf-813e-d0cce4f93862
  spec:
    sourcePod: network-check-source-8894fc9bd-4h869
    targetEndpoint: aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T15:04:40Z"
      message: 'load-balancer-api-external: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.662709ms
      message: 'load-balancer-api-external: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:28:40Z"
    - latency: 6.632387ms
      message: 'load-balancer-api-external: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:28:40Z"
    - latency: 4.099903ms
      message: 'load-balancer-api-external: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:27:40Z"
    - latency: 7.185471ms
      message: 'load-balancer-api-external: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:27:40Z"
    - latency: 5.567651ms
      message: 'load-balancer-api-external: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 6.386416ms
      message: 'load-balancer-api-external: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 4.762516ms
      message: 'load-balancer-api-external: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 6.585599ms
      message: 'load-balancer-api-external: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 4.587807ms
      message: 'load-balancer-api-external: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:24:40Z"
    - latency: 7.429233ms
      message: 'load-balancer-api-external: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-249-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-249.ec2.internal
      uid: 3c7237c1-4ad0-4cd5-8e26-704dde9e6aa0
    resourceVersion: "44699"
    uid: 983b9113-2659-4432-a154-2408c27a065d
  spec:
    sourcePod: network-check-source-8894fc9bd-4h869
    targetEndpoint: aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T15:04:40Z"
      message: 'load-balancer-api-internal: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.647714ms
      message: 'load-balancer-api-internal: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:28:40Z"
    - latency: 6.547632ms
      message: 'load-balancer-api-internal: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:28:40Z"
    - latency: 4.439673ms
      message: 'load-balancer-api-internal: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:27:40Z"
    - latency: 7.152341ms
      message: 'load-balancer-api-internal: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:27:40Z"
    - latency: 5.554921ms
      message: 'load-balancer-api-internal: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 6.307351ms
      message: 'load-balancer-api-internal: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 4.768258ms
      message: 'load-balancer-api-internal: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 6.53798ms
      message: 'load-balancer-api-internal: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 4.515204ms
      message: 'load-balancer-api-internal: tcp connection to aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:24:40Z"
    - latency: 7.384531ms
      message: 'load-balancer-api-internal: resolved host name aa6e19fd61f3c43cca21c9948c8a50d8-8203fbc83a641143.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-130-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-249.ec2.internal
      uid: 3c7237c1-4ad0-4cd5-8e26-704dde9e6aa0
    resourceVersion: "42991"
    uid: 5fbd3919-a2bb-4473-8888-4f223d2168a5
  spec:
    sourcePod: network-check-source-8894fc9bd-4h869
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T15:05:40Z"
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.526351ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 804.994µs
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 913.431µs
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:24:40Z"
    - latency: 1.383029ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:23:40Z"
    - latency: 758.886µs
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:22:40Z"
    - latency: 827.164µs
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:21:40Z"
    - latency: 867.282µs
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:20:40Z"
    - latency: 1.339483ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:19:40Z"
    - latency: 897.438µs
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:18:40Z"
    - latency: 929.74µs
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:17:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-133-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-249.ec2.internal
      uid: 3c7237c1-4ad0-4cd5-8e26-704dde9e6aa0
    resourceVersion: "42993"
    uid: 1761648f-9ea9-4558-8885-cfc8b0853e44
  spec:
    sourcePod: network-check-source-8894fc9bd-4h869
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T15:05:40Z"
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.316255ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 1.954714ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 1.69486ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:24:40Z"
    - latency: 1.874247ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:23:40Z"
    - latency: 1.99869ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:22:40Z"
    - latency: 2.054873ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:21:40Z"
    - latency: 2.25726ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:20:40Z"
    - latency: 2.138846ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:19:40Z"
    - latency: 1.975054ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:18:40Z"
    - latency: 1.76423ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:17:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-141-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-249.ec2.internal
      uid: 3c7237c1-4ad0-4cd5-8e26-704dde9e6aa0
    resourceVersion: "42992"
    uid: 4cd68fc4-3204-4d7e-b1bb-71f4385c8fb0
  spec:
    sourcePod: network-check-source-8894fc9bd-4h869
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T15:05:40Z"
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.272332ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 2.264823ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 2.155291ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:24:40Z"
    - latency: 1.967931ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:23:40Z"
    - latency: 2.316345ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:22:40Z"
    - latency: 2.052856ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:21:40Z"
    - latency: 1.823088ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:20:40Z"
    - latency: 2.156767ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:19:40Z"
    - latency: 2.010933ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:18:40Z"
    - latency: 1.993328ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:17:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-249-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-249.ec2.internal
      uid: 3c7237c1-4ad0-4cd5-8e26-704dde9e6aa0
    resourceVersion: "44697"
    uid: d444f75b-a869-445d-9737-1fee436e2a04
  spec:
    sourcePod: network-check-source-8894fc9bd-4h869
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T15:04:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 754.455µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:28:40Z"
    - latency: 1.860613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:28:40Z"
    - latency: 1.013888ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:27:40Z"
    - latency: 1.627129ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:27:40Z"
    - latency: 763.627µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 1.702319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:26:40Z"
    - latency: 951.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 1.772866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:25:40Z"
    - latency: 814.579µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:24:40Z"
    - latency: 1.681486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:24:40Z"
kind: List
metadata:
  resourceVersion: ""