apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:54:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-28-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-28.ec2.internal
      uid: efd0a650-20f3-449b-aa9d-4ed7e84c9029
    resourceVersion: "17841"
    uid: b4a6eaaa-d12c-4c7a-9405-29453f83b266
  spec:
    sourcePod: network-check-source-7cbc45fddc-bnpgn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:01:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.334µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:08:03Z"
    - latency: 895.488µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:07:03Z"
    - latency: 1.128556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:06:03Z"
    - latency: 1.024513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:05:03Z"
    - latency: 891.261µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:04:03Z"
    - latency: 1.281042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:03:03Z"
    - latency: 1.470096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:03Z"
    - latency: 959.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:03Z"
    - latency: 1.090894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:03Z"
    - latency: 994.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:54:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-28-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-28.ec2.internal
      uid: efd0a650-20f3-449b-aa9d-4ed7e84c9029
    resourceVersion: "19731"
    uid: fb7e8c4a-5e10-4f01-897a-bdd72c84ada6
  spec:
    sourcePod: network-check-source-7cbc45fddc-bnpgn
    targetEndpoint: a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:00:03Z"
      message: 'load-balancer-api-external: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.259034ms
      message: 'load-balancer-api-external: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:12:03Z"
    - latency: 6.605583ms
      message: 'load-balancer-api-external: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:12:03Z"
    - latency: 4.599576ms
      message: 'load-balancer-api-external: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:11:03Z"
    - latency: 7.053667ms
      message: 'load-balancer-api-external: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:11:03Z"
    - latency: 5.790358ms
      message: 'load-balancer-api-external: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:10:03Z"
    - latency: 6.428049ms
      message: 'load-balancer-api-external: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:10:03Z"
    - latency: 5.235442ms
      message: 'load-balancer-api-external: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:09:03Z"
    - latency: 7.08925ms
      message: 'load-balancer-api-external: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:09:03Z"
    - latency: 3.599077ms
      message: 'load-balancer-api-external: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:08:03Z"
    - latency: 6.521709ms
      message: 'load-balancer-api-external: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:08:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:54:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-28-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-28.ec2.internal
      uid: efd0a650-20f3-449b-aa9d-4ed7e84c9029
    resourceVersion: "19730"
    uid: 32744ace-d828-4d90-88ff-d349833f5221
  spec:
    sourcePod: network-check-source-7cbc45fddc-bnpgn
    targetEndpoint: a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:00:03Z"
      message: 'load-balancer-api-internal: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.28257ms
      message: 'load-balancer-api-internal: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:12:03Z"
    - latency: 6.519064ms
      message: 'load-balancer-api-internal: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:12:03Z"
    - latency: 4.763672ms
      message: 'load-balancer-api-internal: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:11:03Z"
    - latency: 7.029496ms
      message: 'load-balancer-api-internal: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:11:03Z"
    - latency: 5.769772ms
      message: 'load-balancer-api-internal: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:10:03Z"
    - latency: 6.358602ms
      message: 'load-balancer-api-internal: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:10:03Z"
    - latency: 5.246891ms
      message: 'load-balancer-api-internal: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:09:03Z"
    - latency: 7.072428ms
      message: 'load-balancer-api-internal: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:09:03Z"
    - latency: 4.18016ms
      message: 'load-balancer-api-internal: tcp connection to a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:08:03Z"
    - latency: 6.485388ms
      message: 'load-balancer-api-internal: resolved host name a14b260474bb743609202486222d65c7-32ef3cd14edcfb0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:08:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:54:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-28-to-network-check-target-ip-10-0-133-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-28.ec2.internal
      uid: efd0a650-20f3-449b-aa9d-4ed7e84c9029
    resourceVersion: "17839"
    uid: 4044ae0a-960a-4a8c-9ef9-01e1d4b91ebe
  spec:
    sourcePod: network-check-source-7cbc45fddc-bnpgn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:01:03Z"
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.373738ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:08:03Z"
    - latency: 2.134611ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:07:03Z"
    - latency: 2.481416ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:06:03Z"
    - latency: 2.613302ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:05:03Z"
    - latency: 2.2691ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:04:03Z"
    - latency: 2.377014ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:03:03Z"
    - latency: 2.741873ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:03Z"
    - latency: 2.67326ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:03Z"
    - latency: 2.271682ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:03Z"
    - latency: 2.935428ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:54:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-28-to-network-check-target-ip-10-0-134-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-28.ec2.internal
      uid: efd0a650-20f3-449b-aa9d-4ed7e84c9029
    resourceVersion: "17837"
    uid: df10b397-c862-4edc-843f-d67072894973
  spec:
    sourcePod: network-check-source-7cbc45fddc-bnpgn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:01:03Z"
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.168µs
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:08:03Z"
    - latency: 981.919µs
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:07:03Z"
    - latency: 1.537126ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:06:03Z"
    - latency: 1.215021ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:05:03Z"
    - latency: 1.102551ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:04:03Z"
    - latency: 1.65991ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:03:03Z"
    - latency: 1.681066ms
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:03Z"
    - latency: 870.77µs
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:03Z"
    - latency: 968.556µs
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:03Z"
    - latency: 946.614µs
      message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:54:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-28-to-network-check-target-ip-10-0-136-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-28.ec2.internal
      uid: efd0a650-20f3-449b-aa9d-4ed7e84c9029
    resourceVersion: "17838"
    uid: 6a5f68dc-66fb-4bdf-a926-56a851ce652f
  spec:
    sourcePod: network-check-source-7cbc45fddc-bnpgn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:01:03Z"
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.933736ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:08:03Z"
    - latency: 2.011181ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:07:03Z"
    - latency: 2.072229ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:06:03Z"
    - latency: 1.988167ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:05:03Z"
    - latency: 2.023963ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:04:03Z"
    - latency: 2.067809ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:03:03Z"
    - latency: 1.751775ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:03Z"
    - latency: 1.987348ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:03Z"
    - latency: 1.842046ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:03Z"
    - latency: 2.019995ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:54:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-28-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-28.ec2.internal
      uid: efd0a650-20f3-449b-aa9d-4ed7e84c9029
    resourceVersion: "19728"
    uid: 4676173a-f509-4371-a2cf-244c38d9afce
  spec:
    sourcePod: network-check-source-7cbc45fddc-bnpgn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:00:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 821.19µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:12:03Z"
    - latency: 1.768354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:12:03Z"
    - latency: 894.264µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:11:03Z"
    - latency: 2.011812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:11:03Z"
    - latency: 945.597µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:10:03Z"
    - latency: 1.717954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:10:03Z"
    - latency: 1.323673ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:09:03Z"
    - latency: 1.795748ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:09:03Z"
    - latency: 1.182641ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:08:03Z"
    - latency: 1.938263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:08:03Z"
kind: List
metadata:
  resourceVersion: ""