apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: a4694282-4800-4184-9e43-833bedcb532d
    resourceVersion: "32185"
    uid: 90086bf5-4ddd-4a1f-abb8-cfe714af675b
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgmm5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 977.427µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 829.287µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 875.757µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 831.843µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:01:44Z"
    - latency: 1.259488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:00:44Z"
    - latency: 912.57µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:59:44Z"
    - latency: 1.183869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:58:44Z"
    - latency: 1.364478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:57:44Z"
    - latency: 913.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: a4694282-4800-4184-9e43-833bedcb532d
    resourceVersion: "32186"
    uid: fce9e979-12e4-4bcf-ba73-c6894fea320a
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgmm5
    targetEndpoint: a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:44Z"
      message: 'load-balancer-api-external: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.940041ms
      message: 'load-balancer-api-external: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 8.467998ms
      message: 'load-balancer-api-external: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 5.731216ms
      message: 'load-balancer-api-external: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 9.928761ms
      message: 'load-balancer-api-external: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 5.457751ms
      message: 'load-balancer-api-external: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 8.042202ms
      message: 'load-balancer-api-external: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 4.798841ms
      message: 'load-balancer-api-external: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 9.190625ms
      message: 'load-balancer-api-external: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 4.704437ms
      message: 'load-balancer-api-external: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:01:44Z"
    - latency: 6.816721ms
      message: 'load-balancer-api-external: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:01:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: a4694282-4800-4184-9e43-833bedcb532d
    resourceVersion: "32187"
    uid: 1002b182-77c0-49d8-a687-ce0f8da327c7
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgmm5
    targetEndpoint: a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:44Z"
      message: 'load-balancer-api-internal: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.937947ms
      message: 'load-balancer-api-internal: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 8.421202ms
      message: 'load-balancer-api-internal: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 5.697777ms
      message: 'load-balancer-api-internal: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 10.00047ms
      message: 'load-balancer-api-internal: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 5.401211ms
      message: 'load-balancer-api-internal: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 7.995454ms
      message: 'load-balancer-api-internal: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 4.783949ms
      message: 'load-balancer-api-internal: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 9.240158ms
      message: 'load-balancer-api-internal: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 4.731108ms
      message: 'load-balancer-api-internal: tcp connection to a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:01:44Z"
    - latency: 6.793504ms
      message: 'load-balancer-api-internal: resolved host name a66a54ab233cd423da24f1af60971b34-ced49ce3e3394a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:01:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-ip-10-0-136-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: a4694282-4800-4184-9e43-833bedcb532d
    resourceVersion: "32182"
    uid: cf5defd1-bcc0-424d-a085-07c55222790a
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgmm5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:44Z"
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.979609ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 2.077742ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 1.641168ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 1.838125ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 1.855896ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:01:44Z"
    - latency: 1.863986ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:00:44Z"
    - latency: 1.851196ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:59:44Z"
    - latency: 1.726904ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:58:44Z"
    - latency: 1.848972ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:57:44Z"
    - latency: 1.787207ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-ip-10-0-137-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: a4694282-4800-4184-9e43-833bedcb532d
    resourceVersion: "32183"
    uid: b8ee07af-597e-4e4c-8209-721e014ad646
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgmm5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:44Z"
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249544ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 2.24825ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 2.072602ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 2.019218ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 1.917206ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:01:44Z"
    - latency: 2.398503ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:00:44Z"
    - latency: 2.178633ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:59:44Z"
    - latency: 2.305034ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:58:44Z"
    - latency: 2.126473ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:57:44Z"
    - latency: 2.08036ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-ip-10-0-140-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: a4694282-4800-4184-9e43-833bedcb532d
    resourceVersion: "32181"
    uid: 8284150e-db9e-4ff5-9d95-b12944fa3f4c
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgmm5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:44Z"
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.915µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 1.06959ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 833.538µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 846.231µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 940.28µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:01:44Z"
    - latency: 1.39217ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:00:44Z"
    - latency: 847.084µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:59:44Z"
    - latency: 1.454887ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:58:44Z"
    - latency: 807.243µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:57:44Z"
    - latency: 929.79µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: a4694282-4800-4184-9e43-833bedcb532d
    resourceVersion: "32184"
    uid: fbadfb0d-a88f-4b79-8dff-ab3685e4ae9a
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgmm5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 777.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 1.986445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:05:44Z"
    - latency: 820.919µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 1.666853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:04:44Z"
    - latency: 1.188664ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 1.715709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:03:44Z"
    - latency: 976.846µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 1.789916ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:02:44Z"
    - latency: 896.1µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:01:44Z"
    - latency: 2.215266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:01:44Z"
kind: List
metadata:
  resourceVersion: ""