apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T14:04:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-155.ec2.internal
      uid: 86dda54a-49b9-4992-8d10-17744453d0ee
    resourceVersion: "69505"
    uid: 8aac58aa-6faf-4fd6-901c-54175e89f8ac
  spec:
    sourcePod: network-check-source-7d88cb55d8-dl9r5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T14:11:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.099706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:53:13Z"
    - latency: 1.032388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 1.080626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 1.04696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 939.14µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 963.205µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:48:13Z"
    - latency: 1.173338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:47:13Z"
    - latency: 1.142591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:46:13Z"
    - latency: 1.234352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:45:13Z"
    - latency: 1.24599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T14:04:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-155.ec2.internal
      uid: 86dda54a-49b9-4992-8d10-17744453d0ee
    resourceVersion: "68297"
    uid: 75acdc6c-6aad-459c-9f88-1b85bd8ee7c5
  spec:
    sourcePod: network-check-source-7d88cb55d8-dl9r5
    targetEndpoint: a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T14:10:13Z"
      message: 'load-balancer-api-external: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.331831ms
      message: 'load-balancer-api-external: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 7.532954ms
      message: 'load-balancer-api-external: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 4.717912ms
      message: 'load-balancer-api-external: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 6.318206ms
      message: 'load-balancer-api-external: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 4.53108ms
      message: 'load-balancer-api-external: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 6.652466ms
      message: 'load-balancer-api-external: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 5.072671ms
      message: 'load-balancer-api-external: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 7.263475ms
      message: 'load-balancer-api-external: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 3.70248ms
      message: 'load-balancer-api-external: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:48:13Z"
    - latency: 7.022964ms
      message: 'load-balancer-api-external: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:48:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T14:04:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-155.ec2.internal
      uid: 86dda54a-49b9-4992-8d10-17744453d0ee
    resourceVersion: "68296"
    uid: e47c6a2c-e451-40dd-9a00-921acf2c0673
  spec:
    sourcePod: network-check-source-7d88cb55d8-dl9r5
    targetEndpoint: a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T14:10:13Z"
      message: 'load-balancer-api-internal: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.341244ms
      message: 'load-balancer-api-internal: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 7.613737ms
      message: 'load-balancer-api-internal: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 4.738113ms
      message: 'load-balancer-api-internal: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 6.265406ms
      message: 'load-balancer-api-internal: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 4.536904ms
      message: 'load-balancer-api-internal: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 6.699572ms
      message: 'load-balancer-api-internal: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 5.114327ms
      message: 'load-balancer-api-internal: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 7.201734ms
      message: 'load-balancer-api-internal: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 3.7503ms
      message: 'load-balancer-api-internal: tcp connection to a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:48:13Z"
    - latency: 7.063183ms
      message: 'load-balancer-api-internal: resolved host name a0357e060425648968993161093e16bb-c015f8fa7d7d0b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:48:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T14:04:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-155-to-network-check-target-ip-10-0-130-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-155.ec2.internal
      uid: 86dda54a-49b9-4992-8d10-17744453d0ee
    resourceVersion: "69504"
    uid: 1d14ec69-e54c-4385-806d-e9e7b3c5e495
  spec:
    sourcePod: network-check-source-7d88cb55d8-dl9r5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T14:11:13Z"
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.485538ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:53:13Z"
    - latency: 2.841014ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 2.573449ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 2.816179ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 2.617362ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 2.563197ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:48:13Z"
    - latency: 2.743337ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:47:13Z"
    - latency: 2.620527ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:46:13Z"
    - latency: 2.755946ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:45:13Z"
    - latency: 2.751408ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T14:04:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-155-to-network-check-target-ip-10-0-131-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-155.ec2.internal
      uid: 86dda54a-49b9-4992-8d10-17744453d0ee
    resourceVersion: "69502"
    uid: 60c06017-51ff-4206-a3a5-e72363499296
  spec:
    sourcePod: network-check-source-7d88cb55d8-dl9r5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T14:11:13Z"
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.185497ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:53:13Z"
    - latency: 2.008057ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 2.39888ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 2.470453ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 2.701827ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 2.415676ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:48:13Z"
    - latency: 2.168482ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:47:13Z"
    - latency: 2.385413ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:46:13Z"
    - latency: 2.462463ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:45:13Z"
    - latency: 2.443814ms
      message: 'network-check-target-ip-10-0-131-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T14:04:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-155-to-network-check-target-ip-10-0-139-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-155.ec2.internal
      uid: 86dda54a-49b9-4992-8d10-17744453d0ee
    resourceVersion: "69503"
    uid: b1a4abd3-bd3e-4316-9766-5500d279e10b
  spec:
    sourcePod: network-check-source-7d88cb55d8-dl9r5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T14:11:13Z"
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.408967ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:53:13Z"
    - latency: 1.058686ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 1.530197ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 978.736µs
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 1.138662ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 963.663µs
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:48:13Z"
    - latency: 1.006664ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:47:13Z"
    - latency: 1.525169ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:46:13Z"
    - latency: 1.189438ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:45:13Z"
    - latency: 1.289682ms
      message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T14:04:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-155.ec2.internal
      uid: 86dda54a-49b9-4992-8d10-17744453d0ee
    resourceVersion: "68295"
    uid: 2081f2d2-0835-48ca-bff7-173bb9433484
  spec:
    sourcePod: network-check-source-7d88cb55d8-dl9r5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T14:10:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 2.500061ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:52:13Z"
    - latency: 1.076243ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 1.918138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:51:13Z"
    - latency: 1.007301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 1.881243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:50:13Z"
    - latency: 964.399µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 1.83087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:49:13Z"
    - latency: 1.035766ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T14:48:13Z"
    - latency: 1.959073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T14:48:13Z"
kind: List
metadata:
  resourceVersion: ""