apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-65-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-65.ec2.internal
      uid: 4d06e2ad-b9fd-40c4-9252-c1e76110e746
    resourceVersion: "29472"
    uid: 5b625a4a-17d2-460e-921d-2731f8823ebe
  spec:
    sourcePod: network-check-source-6f78d59f99-qvd5x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.855866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:09:04Z"
    - latency: 1.108194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:08:04Z"
    - latency: 802.322µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 1.039809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 1.238984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 1.205126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 1.124799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:03:04Z"
    - latency: 1.268384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:02:04Z"
    - latency: 1.220862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:01:04Z"
    - latency: 1.585545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:00:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-65-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-65.ec2.internal
      uid: 4d06e2ad-b9fd-40c4-9252-c1e76110e746
    resourceVersion: "26470"
    uid: 27056d3c-7f2e-494d-bd91-7c5245e969fc
  spec:
    sourcePod: network-check-source-6f78d59f99-qvd5x
    targetEndpoint: a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:01:04Z"
      message: 'load-balancer-api-external: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.46247ms
      message: 'load-balancer-api-external: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 9.009948ms
      message: 'load-balancer-api-external: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 15.628349ms
      message: 'load-balancer-api-external: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 9.018474ms
      message: 'load-balancer-api-external: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 33.496593ms
      message: 'load-balancer-api-external: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 7.539508ms
      message: 'load-balancer-api-external: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 16.02811ms
      message: 'load-balancer-api-external: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 7.331584ms
      message: 'load-balancer-api-external: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 14.151834ms
      message: 'load-balancer-api-external: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:03:04Z"
    - latency: 9.234477ms
      message: 'load-balancer-api-external: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:03:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-65-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-65.ec2.internal
      uid: 4d06e2ad-b9fd-40c4-9252-c1e76110e746
    resourceVersion: "26471"
    uid: 39ab276b-673a-4597-922b-b02a0487e165
  spec:
    sourcePod: network-check-source-6f78d59f99-qvd5x
    targetEndpoint: a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:01:04Z"
      message: 'load-balancer-api-internal: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.597428ms
      message: 'load-balancer-api-internal: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 8.967075ms
      message: 'load-balancer-api-internal: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 14.032404ms
      message: 'load-balancer-api-internal: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 9.042445ms
      message: 'load-balancer-api-internal: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 32.349699ms
      message: 'load-balancer-api-internal: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 7.469222ms
      message: 'load-balancer-api-internal: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 16.015805ms
      message: 'load-balancer-api-internal: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 7.263417ms
      message: 'load-balancer-api-internal: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 13.424742ms
      message: 'load-balancer-api-internal: tcp connection to a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:03:04Z"
    - latency: 9.14734ms
      message: 'load-balancer-api-internal: resolved host name a73fc62f14d6b45708b9d56e133dd2dc-e5bd39875fc21fbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:03:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-65-to-network-check-target-ip-10-0-135-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-65.ec2.internal
      uid: 4d06e2ad-b9fd-40c4-9252-c1e76110e746
    resourceVersion: "29470"
    uid: c46d8fc8-1dcd-483c-a175-65eaa95f67d4
  spec:
    sourcePod: network-check-source-6f78d59f99-qvd5x
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:04Z"
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.912382ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:09:04Z"
    - latency: 2.311039ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:08:04Z"
    - latency: 2.548796ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 2.166417ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 2.274772ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 2.485078ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 2.491316ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:03:04Z"
    - latency: 2.662559ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:02:04Z"
    - latency: 2.274056ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:01:04Z"
    - latency: 2.060935ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:00:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-65-to-network-check-target-ip-10-0-138-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-65.ec2.internal
      uid: 4d06e2ad-b9fd-40c4-9252-c1e76110e746
    resourceVersion: "29469"
    uid: b8edba1e-bc31-4aac-9373-1164d117c651
  spec:
    sourcePod: network-check-source-6f78d59f99-qvd5x
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:04Z"
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.638411ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:09:04Z"
    - latency: 2.255883ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:08:04Z"
    - latency: 1.950293ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 2.830739ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 2.051694ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 2.043705ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 2.477613ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:03:04Z"
    - latency: 2.036287ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:02:04Z"
    - latency: 1.987522ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:01:04Z"
    - latency: 1.995817ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:00:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-65-to-network-check-target-ip-10-0-140-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-65.ec2.internal
      uid: 4d06e2ad-b9fd-40c4-9252-c1e76110e746
    resourceVersion: "29468"
    uid: 81305df4-458e-4cf7-8744-944f003e57ad
  spec:
    sourcePod: network-check-source-6f78d59f99-qvd5x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:04Z"
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.651012ms
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:09:04Z"
    - latency: 805.828µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:08:04Z"
    - latency: 795.141µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 1.033955ms
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 829.435µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 790.861µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 860.401µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:03:04Z"
    - latency: 923.829µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:02:04Z"
    - latency: 753.77µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:01:04Z"
    - latency: 700.709µs
      message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:00:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-65-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-65.ec2.internal
      uid: 4d06e2ad-b9fd-40c4-9252-c1e76110e746
    resourceVersion: "26468"
    uid: 11a297e1-381c-419e-91c1-1841d48a86a8
  spec:
    sourcePod: network-check-source-6f78d59f99-qvd5x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:01:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.123426ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 1.668784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:07:04Z"
    - latency: 840.347µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 2.862727ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:06:04Z"
    - latency: 1.182949ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 1.990947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:05:04Z"
    - latency: 1.057808ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 1.795652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:04:04Z"
    - latency: 1.025681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:03:04Z"
    - latency: 2.066922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:03:04Z"
kind: List
metadata:
  resourceVersion: ""